WP Easy Toggles CVE-2025-10190
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor-level account
-
DeliveryInsert malicious 'toggles' shortcode attributes
-
ExploitScript stored unsanitized in page
-
ExecutionVictim views injected page
-
ImpactArbitrary script executes in victim browser
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 an authenticated account with contributor-level capability or higher on the target WordPress site, and the WP Easy Toggles plugin (version ≤1.9.0) must be installed and active so the 'toggles' shortcode is available. The injection occurs through user-supplied attributes passed to that specific shortcode, which the plugin fails to sanitize on input or escape on output. The payload only executes when another user (visitor, editor, or administrator) subsequently accesses the page containing the injected shortcode, so impact depends on that page being viewed. Primary limiting factors: the contributor-account prerequisite (PR:L) means anonymous attackers cannot exploit it directly, making open/untrusted user registration the main risk amplifier; no special non-default configuration is otherwise needed beyond having the plugin active. |
| Impact | This is a moderate-severity stored XSS (CVSS 6.4, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) that is a real but low-urgency issue rather than an emergency. The CVSS vector confirms network attack vector, low complexity, and NO user interaction for injection, but critically requires PR:L - the attacker must already hold an authenticated contributor-level (or higher) account, which meaningfully narrows the realistic attacker population. The scope change (S:C) reflects that injected scripts execute in the browser context of other users/visitors, raising impact above a self-contained flaw, though confidentiality and integrity impacts are only Low and availability is None. All signals agree this is low-to-moderate real-world priority: EPSS is 0.23% (13th percentile), indicating low predicted exploitation likelihood; there is no CISA KEV listing and no public exploit code identified. There is no conflict between signals - the low EPSS, absence of KEV, and the authentication prerequisite are mutually consistent with a vulnerability that is genuine but not a mass-exploitation target. The main caveat is trust model: sites that allow untrusted contributor registrations face more exposure than those where contributor accounts are tightly controlled. |
| Exploit ScenarioDerived | An attacker who holds or obtains a contributor-level WordPress account crafts a post or page using the plugin's 'toggles' shortcode with malicious attribute values containing JavaScript, which is stored without sanitization. When an administrator, editor, or site visitor later views that page, the script executes in their browser, enabling session/cookie theft or actions in the victim's context. No public proof-of-concept exploit has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Stored cross-site scripting in the WP Easy Toggles plugin for WordPress (all versions up to and including 1.9.0) allows authenticated attackers holding contributor-level access or higher to inject arbitrary JavaScript through unsanitized attributes on the plugin's 'toggles' shortcode; the script persists in the page content and executes in the browser of any visitor, editor, or administrator who later views that page. The issue is a CWE-79 input-sanitization and output-escaping failure rated CVSS 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), with scope change reflecting that the injected script runs in the context of higher-privileged users. Risk is real but low-urgency: EPSS is only 0.23% (13th percentile), no public exploit code was identified at time of analysis, and exploitation is gated behind a contributor account, making open or untrusted user registration the primary amplifier.
RemediationAI
No vendor-released patch or fixed version is identified in the available data - version 1.9.0 appears to be the current release - so the primary actions are compensating controls rather than an upgrade. First, if the toggles functionality is not essential, deactivate and delete the WP Easy Toggles plugin; this removes the vulnerable shortcode entirely and has no side effect other than losing the toggle UI. Second, if the plugin must stay active, restrict the ability to publish shortcode content: remove or downgrade untrusted contributor accounts, disable open registration and any 'contributor' auto-assignment, and require editorial review so the 'toggles' shortcode only appears on pages authored by trusted users - the trade-off is reduced publishing throughput and a workflow change for site editors. Third, deploy output-side hardening such as a WordPress security plugin or web application firewall rule set that filters XSS patterns in post content, and consider a Content-Security-Policy header that blocks inline script execution; CSP can break legitimate theme or plugin scripts, so test in report-only mode first. Finally, monitor the plugin's WordPress.org page and the Wordfence threat intelligence record at https://www.wordfence.com/threat-intel/vulnerabilities/id/5a9db562-6810-4da1-9e5f-6f6eadca76ac?source=cve for a patched release, and audit existing posts for injected scripts before and after any fix is applied.
Affected ProductsAI
The affected product is the WordPress plugin WP Easy Toggles, and per the description every release up to and including version 1.9.0 is vulnerable, with no fixed version named in the available data. The canonical product listing is the WordPress.org plugin page at https://wordpress.org/plugins/wp-easy-toggles, and the suspect implementation is visible in the plugin source at https://plugins.trac.wordpress.org/browser/wp-easy-toggles/trunk/wp-easy-toggles.php#L31. Any WordPress site with the plugin installed and active is in scope, and the attack surface is specifically any post, page, or custom post type where the 'toggles' shortcode can be authored - which in default configurations includes contributor-level accounts. No CPE identifiers were provided with this record, so version confirmation should be performed directly against the installed plugin directory on each site.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WordPress shortcodes are bracketed macros such as [toggles] that are expanded server-side into HTML when post content is rendered. In WP Easy Toggles, the attributes supplied inside the shortcode are neither sanitized at input time nor escaped when emitted into the page, so an attacker who can create or edit post content can place markup or script-bearing attribute values that survive storage and are replayed into the DOM on every subsequent page view - the defining pattern of CWE-79 stored (persistent) cross-site scripting. The CVSS 3.1 vector confirms the relevant conditions: AV:N (reachable over the network), AC:L (no special conditions), PR:L (authenticated, low privilege - contributor or above per the description), UI:N (no victim interaction beyond visiting the page), and S:C (a scope change, because code injected by a low-privileged author executes in the security context of the page and can target administrators or editors). The NVD reference to line 31 of wp-easy-toggles.php in the plugin's Trac browser points at the shortcode handling code path implicated in the missing escaping; no CPE strings were supplied, so affected-product identification relies on the plugin slug 'wp-easy-toggles' and its WordPress.org directory entry.
Know when Wordpress Plugin 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:N/S:C/C:L/I:L/A:N
Stored XSS reachable over the network with low-privilege contributor account (PR:L), no interaction to inject, scope change (S:C) since scripts run in other users' browsers, with Low C/I and no availability impact.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
The WP Easy Toggles plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'toggles' shortcode in all versions up to, and including, 1.9.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB