Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister subscriber account on target site
-
DeliveryInject XSS payload into accordion content field
-
ExploitSave malicious accordion item
-
ExecutionLure or wait for admin to view page
-
PersistScript executes in admin browser context
-
ImpactExfiltrate session cookie or perform admin action
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to hold at minimum a WordPress subscriber-level account on the target site (PR:L per CVSS), which is only obtainable if the site has open user registration enabled or the attacker has been granted an account by another means. A privileged user - typically an administrator or editor - must actively visit or preview the page containing the injected accordion content (UI:R per CVSS). Limiting factors: sites with closed registration (invite-only or no self-registration) are not exploitable remotely without pre-existing credentials; the Accordion plugin must be installed and active; and the injected content must be on a page that a privileged user is likely to view. The attack does not require any non-default server configuration beyond having the plugin installed and user registration open. |
| Impact | The CVSS 6.5 Medium score is generally appropriate for this class of vulnerability. The CVSS vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) shows low attack complexity with subscriber-level authentication required and mandatory victim interaction - these are meaningful limiting factors. The PR:L requirement means an attacker must obtain at least a subscriber account, which is only feasible on WordPress sites that permit public user registration. The UI:R component means exploitation is not fully autonomous - a privileged user must navigate to the poisoned page. No EPSS score is provided in the input data, and no KEV listing or public POC is reported, so real-world exploitation urgency is lower than a comparable unauthenticated stored XSS. The A:L (availability) metric in the official vector is atypical for XSS and is likely overstated; XSS does not generally cause availability loss to the server. Priority should be elevated for sites with open registration or multi-author environments where subscriber accounts are widely held. |
| Exploit ScenarioDerived | An attacker registers a subscriber account on a WordPress site with public registration enabled, then navigates to the Accordion plugin's content editor and injects a JavaScript payload - such as a cookie-stealing script - into an accordion item title or body field. When a logged-in administrator later views the page containing the poisoned accordion, the script executes in their browser, exfiltrating the admin session cookie to an attacker-controlled endpoint and enabling full site takeover. No public POC has been identified at time of analysis, but the attack requires no special tooling beyond a browser. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 13, 2026
Stored Cross-Site Scripting in the Accordion WordPress plugin (versions <= 3.0.6) allows authenticated subscriber-level users to inject malicious JavaScript into accordion content fields, which then executes in the browser of any higher-privileged user who views the affected page. The scope change (S:C in CVSS) confirms the attack pivots from the subscriber's input to the victim's browsing session, enabling session hijacking, credential theft, or unauthorized admin actions. No public exploit code or CISA KEV listing is identified at time of analysis, but the low attack complexity and subscriber-level access requirement make this a realistic threat on sites with open user registration.
RemediationAI
Update the Accordion plugin to the first version released after 3.0.6 as soon as one is available from the WordPress plugin repository or ThemePoints directly; no specific patched version number is confirmed from the available input data, so administrators should verify the current release via the WordPress admin dashboard or the Patchstack advisory at the reference URL. As an interim compensating control, disable public user registration (Settings > General > uncheck 'Anyone can register') to eliminate the subscriber-level account creation vector, accepting the trade-off that legitimate self-registration is blocked. Alternatively, restrict accordion content editing capabilities to Editor-level or higher roles via a role management plugin such as Members or User Role Editor, which limits which users can submit the vulnerable fields. Deploying a web application firewall rule that blocks common XSS payloads in POST parameters to the plugin's save endpoints can add a detection and blocking layer but is not a substitute for patching.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-79 (Improper Neutralization of Input During Web Page Generation) describes insufficient output encoding of user-supplied data before rendering in a browser context. The affected product, identified via CPE cpe:2.3:a:themepoints:accordion:*:*:*:*:*:*:*:*, is a WordPress plugin by ThemePoints that provides collapsible accordion UI components. The vulnerability originates from the plugin's failure to sanitize or escape subscriber-controlled input - such as accordion item titles or body text - prior to rendering it in the page HTML. Because WordPress subscriber accounts have limited trust by design, any plugin that grants them write access to fields later reflected in the DOM without proper escaping creates a stored XSS surface. The scope change (S:C) indicates the injected payload executes in the victim's browser security context rather than the server's, which is characteristic of client-side XSS payloads.
Know when Accordion gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
A:N replaces A:L from the official vector because stored XSS does not cause server-side availability loss; all other metrics are consistent with subscriber-initiated stored XSS requiring victim interaction.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Cross Site Scripting (XSS) in Accordion <= 3.0.6 versions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
The Accordion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'tcpaccordion' shortcod
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themepoints Accord
The tab GET parameter of the settings page is not sanitised or escaped when being output back in an HTML attribute, lead
An issue was discovered in the Accordion plugin before 2.2.9 for WordPress. Rated medium severity (CVSS 5.4), this vulne
PHP object injection (CWE-502) in the PickPlugins Accordion WordPress plugin through version 2.3.25 lets an administrato
EUVD-2026-57889
GHSA-vhmj-c5j6-939q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB