Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend HTTP request with scripted REQUEST_URI
-
DeliveryPayload stored unsanitized in Activity Log
-
ExploitAdmin opens Activity Log settings page
-
ExecutionScript executes in admin browser session
-
ImpactHijack session or perform admin actions
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 the target running Automatic.css exactly at version 4.0.0 with its Activity Log feature active. The attacker injects a script into the REQUEST_URI of an HTTP request to the site (per the description, no authentication is needed for injection, though the CVSS vector's PR:L contradicts this). Exploitation is gated on victim interaction: the payload only executes when an authenticated administrator subsequently opens the Activity Log settings page in wp-admin, which limits reliability and timing. Scope is limited to a single plugin version and to sites where an admin actually reviews the activity log. |
| Impact | This is a stored XSS (CWE-79) in Automatic.css 4.0.0 where the plugin logs the raw REQUEST_URI into its Activity Log without sanitization, then renders it unescaped on the admin Activity Log settings page. The vendor CVSS of 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reflects network reach, low complexity, and a scope change into the admin's authenticated browser session. There is a material internal conflict in the source data: the description states 'unauthenticated attackers' can inject the payload, yet the CVSS vector encodes PR:L (attacker privileges required) and UI:N (no user interaction) - these are inconsistent, since a REQUEST_URI-logging sink is reachable pre-authentication and the payload only fires when an admin later views the log page (victim interaction). Treating the description as authoritative, this is an unauthenticated stored XSS whose payoff is gated on an administrator opening the Activity Log page. No EPSS score, no CISA KEV listing, and no public POC were provided, so despite the medium CVSS this is not a demonstrated priority: exploitation is plausible and low-complexity but currently theoretical (no public exploit identified at time of analysis), and confined to a niche commercial plugin at a single version. Net: medium-severity, low real-world urgency pending patch, but worth prompt updating for sites running the exact affected build because unauthenticated injection into an admin-viewed page is a credible account-takeover vector. |
| Exploit ScenarioDerived | An attacker sends a crafted HTTP request to a site running Automatic.css 4.0.0 with a JavaScript payload embedded in the request URI; the plugin's logger records the raw REQUEST_URI into the Activity Log. When a logged-in administrator later opens the Activity Log settings page in wp-admin, the stored script executes in their authenticated session, enabling session/cookie theft or admin-privileged actions. No public exploit code was identified at time of analysis, and success depends on an administrator viewing the log. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 26, 2026
Stored cross-site scripting in the Automatic.css WordPress plugin 4.0.0 lets an attacker write an unsanitized REQUEST_URI into the plugin's Activity Log, which is then rendered without escaping on the Activity Log settings page, executing arbitrary script in the browser of any administrator who opens that page. The flaw is confined to a single plugin version and only fires when the Activity Log feature is enabled and an admin actually reviews the log, so reliability and timing are attacker-controlled constraints; the vendor-assigned CVSS 3.1 base score is 6.4. No public exploit code was identified at time of analysis and there is no CISA KEV entry, and the analyst-assessed vector (PR:N/UI:R) differs from the supplied vector (PR:L/UI:N), so the exact authentication prerequisite for the injection step remains disputed in the available data.
RemediationAI
No vendor-released patch version is identified in the available data, so the primary action is to check the vendor changelog at https://automaticcss.com/changelogs/ and the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/07d697c5-1c15-4d3a-8637-cc4fd408f209?source=cve for a fixed release, then update Automatic.css beyond 4.0.0 as soon as one is published; if no fixed release exists yet, deactivate and remove the plugin from any site where the Activity Log is not essential, since removing it eliminates the sink entirely at the cost of losing the CSS utility features. As a targeted workaround rather than generic hardening, disable the plugin's Activity Log setting so the tainted REQUEST_URI is never persisted and never rendered - the trade-off is loss of audit/activity visibility for the site. Because the injection vector is the request URI, an upstream WAF or reverse-proxy rule that rejects or normalizes requests whose URI contains angle brackets, script fragments, or encoded equivalents before they reach WordPress can break the injection chain, though such rules risk false positives on legitimate URLs and cannot fix payloads already stored in the log table. Restricting wp-admin access to a trusted IP range or adding administrator re-authentication and short session lifetimes reduces the window and blast radius of a successful stored payload, and administrators who suspect prior exposure should clear the plugin's activity log records so no stored payload remains. Each of these is a compensating control only and does not substitute for upgrading once the vendor ships a fix.
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 issue is a classic CWE-79 cross-site scripting root cause: the plugin captures the raw HTTP REQUEST_URI and passes it to its logger (classes/Helpers/Logger.php) without sanitization, serializes the entry through its WideEvents JSON formatter (classes/Lib/WideEvents/Formatter/JsonFormatter.php), persists it, and then echoes it back unescaped in the admin Activity Log UI (classes/UI/Settings_Page/Activity_Log.php, referenced at line 90), with the logging path wired up in classes/Plugin.php around line 175. Because the stored payload is later served inside the wp-admin interface, the CVSS scope change (S:C) reflects that script executing in an administrator's authenticated session can act on resources beyond the vulnerable plugin component itself, even though confidentiality and integrity impact are each rated Low. The CPE cpe:2.3:a:automatic.css:automatic.css confirms this is the vendor's own WordPress plugin distribution rather than a theme or core component, and the affected code lives in the plugin's Activity Log / logger subsystem, not in its CSS generation features.
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
Description states unauthenticated injection (PR:N); payload fires only when an admin views the log (UI:R); execution in admin browser crosses a trust boundary (S:C) with limited C/I impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Automatic.css plugin for WordPress is vulnerable to Stored Cross-Site Scripting via REQUEST_URI in all version 4.0.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that will execute whenever an administrator accesses the Activity Log settings 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
EUVD-2026-87526
GHSA-xhhf-8p83-jrh4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB