CVE-2026-2352
The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ao_post_preload' meta value in all versions up to, and including, 3.1.14.
Published Mar 21, 2026 · updated Jun 17, 2026
The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ao_post_preload' meta value in all versions up to, and including, 3.1.14. This is due to insufficient input sanitization in the function and missing output escaping when the value is rendered into a tag in . 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, granted the "Image optimization" or "Lazy-load images" setting is enabled in the plugin configuration.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Mar 21, 2026 · NIST NVD
Detected
The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ao_post_preload' meta value in all versions up to, and including, 3.1.14. This is due to insufficient input sanitization in the function and missing output escaping when the value is rendered into a tag in . This makes it possible for authenticated attackers, with Contributor-level access and above, to injec
Jun 17, 2026 · NIST NVD
Updated
The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ao_post_preload' meta value in all versions up to, and including, 3.1.14. This is due to insufficient input sanitization in the function and missing output escaping when the value is rendered into a tag in . This makes it possible for authenticated attackers, with Contributor-level access and above, to injec
Sources
- CVE.orgVulnerability recordCVE-2026-2352
Official CVE identifier
cve.org - NIST NVDVulnerability recordCVE-2026-2352
The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'ao_post_preload' meta value in all versions up to, and including, 3.1.14. This is due to insufficient input sanitization in the function and missing output escaping when
nvd.nist.gov