Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Administrator access to wp-admin
-
DeliveryInject script into Assignment Engine field
-
ExploitPayload stored in plugin block data
-
ExecutionAdmin opens CJT block edit screen
-
ImpactScript executes in dashboard browser context
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 | Requires an authenticated WordPress user with Administrator-level access or above to store the payload in the CSS & JavaScript Toolbox 'Assignment Engine' fields - specifically Expressions, URLs, or Advanced assignment data. Execution is further gated on a user (in practice another admin-area user) subsequently opening the CJT block edit screen in the wp-admin dashboard. Limiting factors: highest-privilege injection prerequisite (PR:H), admin-only victim surface, and the fact that an Administrator can already legitimately inject scripts through this plugin's intended functionality, sharply reducing added impact. Affects all versions up to and including 12.0.6. |
| Impact | This is a low-priority issue despite the CWE-79 stored XSS classification. The vendor CVSS of 4.4 (AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N) is driven down by PR:H, which the description substantiates: exploitation requires Administrator-level access or above to write the malicious payload into the Assignment Engine fields (Expressions, URLs, Advanced assignment data). No EPSS score, no CISA KEV listing, and no public exploit code were provided - so this is 'no public exploit identified at time of analysis.' The payload only fires when a user opens the CJT block edit screen inside the wp-admin dashboard, meaning both the injector and the victim are privileged admin-area users; this is effectively an admin-on-admin (near-self-XSS) condition with little privilege gain, since an Administrator can already inject arbitrary JS/CSS via this plugin's core function. The vendor's UI:N is questionable - the description explicitly conditions execution on a user navigating to the block edit screen, which is user interaction; I assess UI:R. The S:C (scope change) is defensible for browser-context XSS crossing the plugin's security authority. Net: real but low real-world risk, gated behind the highest privilege tier. |
| Exploit ScenarioDerived | An attacker who has already obtained WordPress Administrator access (e.g., via a compromised admin account or a second-stage foothold) injects a malicious script into an Assignment Engine field such as an Expression or URL. The stored payload then executes in the browser of any admin who later opens the CJT block edit screen, enabling session/cookie theft or admin-dashboard actions. No public POC was provided in the input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Stored cross-site scripting in the WordPress plugin CSS & JavaScript Toolbox (all versions up to and including 12.0.6) lets an authenticated user with Administrator-level access persist arbitrary JavaScript through the plugin's Assignment Engine fields - Expressions, URLs, and Advanced assignment data - which is later executed when an administrator opens the CJT block edit screen in wp-admin. Because the injection prerequisite is already Administrator-level access, and an Administrator can legitimately place script and CSS content through this plugin's intended functionality, the marginal impact is small, making this a low-priority issue despite the stored XSS classification. No public exploit code has been identified at time of analysis, and the flaw maps to CWE-79 (improper neutralization of input during web page generation).
RemediationAI
Patch status: upstream fix available (repository commit/changeset, e.g. https://plugins.trac.wordpress.org/changeset?reponame=&old=3667323%40css-javascript-toolbox&new=3667323%40css-javascript-toolbox); a released, tagged patched version is not independently confirmed in the provided data, so administrators should update to the first CSS & JavaScript Toolbox release published after 12.0.6 and verify the installed version no longer matches the affected range. If the plugin is not actively needed, deactivating and deleting it removes the attack surface entirely and is the lowest-risk option where CJT functionality is not in use. Where a patched release is not yet deployable and the plugin must stay enabled, compensating controls should target the Administrator prerequisite that the assessment identifies as the main limiting factor: enforce least privilege by keeping the number of Administrator accounts to the minimum required, audit and remove dormant or shared admin accounts, and enable two-factor authentication for all administrators - recognizing that these reduce the pool of potential injectors but do not stop a determined administrator. Administrators can also review the Assignment Engine entries (Expressions, URLs, and Advanced assignment data) of any existing CJT blocks for unexpected script content and clear suspicious entries, though this is a detection/mitigation measure and not a boundary control, and it will not prevent future injection by an admin-level user. Restricting wp-admin access by IP or a reverse proxy adds further friction for external attackers but introduces operational overhead for legitimate administrators.
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
The vulnerability is a classic CWE-79 stored cross-site scripting flaw in a WordPress plugin that exists to manage CSS and JavaScript blocks for a site. The Assignment Engine within CSS & JavaScript Toolbox accepts structured configuration data - Expressions, URLs, and an 'Advanced' assignment payload - and stores it without sufficient input sanitization, then renders it without adequate output escaping when the block edit screen is displayed. The block-ajax.php controller (the referenced line 184 in both trunk and the 12.0.6 tag) is the code path implicated, meaning the assignment data flows through an AJAX handler into persistent storage and back out into the admin dashboard UI. Because the sink is the wp-admin CJT block edit screen rather than the public-facing front end, execution is confined to authenticated administrator sessions viewing that screen. The affected package is identified by CPE cpe:2.3:a:wipeoutmedia:css_&_javascript_toolbox, covering every release through 12.0.6; a repository changeset (3667323) indicates the underlying sanitization/escaping was subsequently modified in the plugin's source.
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:H/PR:H/UI:N/S:C/C:L/I:L/A:N
Administrator injection makes PR:H; execution needs a victim to open the block edit screen so UI:R; storing a payload is straightforward so AC:L; browser-context XSS gives C:L/I:L and S:C.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The CSS & JavaScript Toolbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 12.0.6 via the Assignment Engine fields. This is due to insufficient input sanitization and output escaping on assignment data fields including Expressions, URLs, and Advanced assignment data. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the CJT block edit screen in the admin dashboard.
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
EUVD-2025-210931
GHSA-6jx6-9xqq-pg98
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB