--- title: "CVE-2026-14995: Autoptimize WordPress Plugin - Stored XSS" description: "Autoptimize WordPress plugin <= 3.1.15.1 contains a stored cross-site scripting caused by insufficient input sanitization and output escaping in REQUEST_URI path, letting unauthenticated attackers inject scripts executed by users, exploit requires Critical CSS feature active with valid API key." url: https://panop.io/threat-heartbeat/CVE-2026-14995/ --- # CVE-2026-14995 Autoptimize WordPress Plugin - Stored XSS Autoptimize WordPress plugin <= 3.1.15.1 contains a stored cross-site scripting caused by insufficient input sanitization and output escaping in REQUEST\_URI path, letting unauthenticated attackers inject scripts executed by users, exploit requires Critical CSS feature active with valid API key. CVSS base score 7.2 /10 High CISA KEV Not listed Public exploit None known Authentication Not required EPSS 0.28% chance of exploitation in 30 days [View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-14995) ## Details Type Stored XSS Impact Stored XSS CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N Published 1 October 2026 Updated 15 October 2026 Weakness [CWE-79](https://cwe.mitre.org/data/definitions/79.html) ## Vendor fix Update to the latest version beyond 3.1.15.1. Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them. ## References - [https://nvd.nist.gov/vuln/detail/CVE-2026-14995](https://nvd.nist.gov/vuln/detail/CVE-2026-14995) - [https://plugins.trac.wordpress.org/changeset?reponame=&old=3713884%40autoptimize&new=3713884%40autoptimize](https://plugins.trac.wordpress.org/changeset?reponame=&old=3713884%40autoptimize&new=3713884%40autoptimize) - [https://www.wordfence.com/threat-intel/vulnerabilities/id/1704cffa-75ed-415e-864f-de7ff8eea8dc?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/1704cffa-75ed-415e-864f-de7ff8eea8dc?source=cve) - [https://plugins.trac.wordpress.org/browser/autoptimize/tags/3.1.15.1/classes/autoptimizeCriticalCSSEnqueue.php#L218](https://plugins.trac.wordpress.org/browser/autoptimize/tags/3.1.15.1/classes/autoptimizeCriticalCSSEnqueue.php#L218) - [https://plugins.trac.wordpress.org/browser/autoptimize/tags/3.1.15.1/classes/autoptimizeCriticalCSSEnqueue.php#L57](https://plugins.trac.wordpress.org/browser/autoptimize/tags/3.1.15.1/classes/autoptimizeCriticalCSSEnqueue.php#L57) - [https://plugins.trac.wordpress.org/browser/autoptimize/tags/3.1.15.1/classes/critcss-inc/admin\_settings\_queue.js.php#L125](https://plugins.trac.wordpress.org/browser/autoptimize/tags/3.1.15.1/classes/critcss-inc/admin_settings_queue.js.php#L125) - [https://plugins.trac.wordpress.org/browser/autoptimize/tags/3.1.15.1/classes/critcss-inc/admin\_settings\_queue.php#L82](https://plugins.trac.wordpress.org/browser/autoptimize/tags/3.1.15.1/classes/critcss-inc/admin_settings_queue.php#L82) [← All CVEs](https://panop.io/threat-heartbeat/) ## What this record can't tell you - Whether you run the affected software, and where - Whether an attacker can actually reach and exploit it - The misconfigurations that never get a CVE number - What it would cost the business, ranked into what to fix first Panop answers these inside your environment, for this CVE and every other finding. [Book a demo](https://panop.io/demo)