CVE-2026-14995: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in optimizingmatters Autoptimize
The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via REQUEST_URI Path in all versions up to, and including, 3.1.15.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the Critical CSS feature to be active with a valid API key configured, as this is the precondition for unauthenticated frontend requests to trigger queue entries via ao_ccss_enqueue().
AI Analysis
Technical Summary
CVE-2026-14995 describes a stored cross-site scripting vulnerability in the Autoptimize WordPress plugin versions up to 3.1.15.1. The vulnerability is due to insufficient input sanitization and output escaping of the REQUEST_URI path, which allows unauthenticated attackers to inject arbitrary web scripts. Successful exploitation depends on the Critical CSS feature being active and configured with a valid API key, as this condition permits unauthenticated frontend requests to trigger queue entries via the ao_ccss_enqueue() function. The vulnerability can lead to script execution in the context of users visiting the affected pages.
Potential Impact
An unauthenticated attacker can inject persistent malicious scripts into pages generated by the Autoptimize plugin, which will execute in the browsers of users who visit those pages. This can lead to information disclosure and integrity impacts as indicated by the CVSS vector (Confidentiality: Low, Integrity: Low, Availability: None). The attack surface is limited to installations with the Critical CSS feature enabled and a valid API key configured.
Mitigation Recommendations
No explicit patch or fix is provided in the available data. Users should check the vendor advisory for updates or patches. Until a fix is available, disabling the Critical CSS feature or removing the API key configuration may mitigate the risk by preventing unauthenticated frontend requests from triggering the vulnerable code path.
CVE-2026-14995: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in optimizingmatters Autoptimize
Description
The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via REQUEST_URI Path in all versions up to, and including, 3.1.15.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the Critical CSS feature to be active with a valid API key configured, as this is the precondition for unauthenticated frontend requests to trigger queue entries via ao_ccss_enqueue().
CVSS v3.1
Score 7.2high
Affected software
optimizingmatters
Autoptimize
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-14995 describes a stored cross-site scripting vulnerability in the Autoptimize WordPress plugin versions up to 3.1.15.1. The vulnerability is due to insufficient input sanitization and output escaping of the REQUEST_URI path, which allows unauthenticated attackers to inject arbitrary web scripts. Successful exploitation depends on the Critical CSS feature being active and configured with a valid API key, as this condition permits unauthenticated frontend requests to trigger queue entries via the ao_ccss_enqueue() function. The vulnerability can lead to script execution in the context of users visiting the affected pages.
Potential Impact
An unauthenticated attacker can inject persistent malicious scripts into pages generated by the Autoptimize plugin, which will execute in the browsers of users who visit those pages. This can lead to information disclosure and integrity impacts as indicated by the CVSS vector (Confidentiality: Low, Integrity: Low, Availability: None). The attack surface is limited to installations with the Critical CSS feature enabled and a valid API key configured.
Mitigation Recommendations
No explicit patch or fix is provided in the available data. Users should check the vendor advisory for updates or patches. Until a fix is available, disabling the Critical CSS feature or removing the API key configuration may mitigate the risk by preventing unauthenticated frontend requests from triggering the vulnerable code path.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-07-07T18:57:46.336Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6abe7481a43b0b3b89bcf0f8
Added to database: 10/01/2026, 14:56:01 UTC
Last enriched: 10/01/2026, 15:11:45 UTC
Last updated: 10/01/2026, 23:06:12 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.