Autoptimize vulnerability records, and where its script, style and image rewriting is set
Autoptimize rewrites what WordPress sends to the browser: its listing says it can aggregate, minify and cache scripts and styles, minify HTML and lazy-load images.
This page reads the records the source data files under its slug by their fields, and shows where its aggregation, exclusion, image and cache-clearing settings sit.
On this page
Autoptimize vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 15 records for Autoptimize. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 3.1.16
Worked out from data retrieved on .
Every affected range listed in this source for Autoptimize ends before version 3.1.16.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Autoptimize <= 3.1.15.1 - Unauthenticated Stored Cross-Site Scripting via Comment Author Name
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.4)
- CVE:
- CVE-2026-78471
Affected versions- All versions up to and including 3.1.15.1
Patched versions: 3.1.16
Update to at least version 3.1.16.
Autoptimize <= 3.1.15.1 - Unauthenticated Stored Cross-Site Scripting via REQUEST_URI Path
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2026-14995
Affected versions- All versions up to and including 3.1.15.1
Patched versions: 3.1.16
Update to at least version 3.1.16.
Multiple Plugins <= Multiple Versions - Unauthenticated Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2026-3220
Affected versions- All versions before 3.1.15
Patched versions: 3.1.15
Update to at least version 3.1.15.
Autoptimize <= 3.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'ao_post_preload' Meta Value
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-2352
Affected versions- All versions up to and including 3.1.14
Patched versions: 3.1.15
Update to at least version 3.1.15.
Autoptimize <= 3.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via Lazy-loaded Image Attributes
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-2430
Affected versions- All versions up to and including 3.1.14
Patched versions: 3.1.15
Update to at least version 3.1.15.
Show 10 older recordsHide the older records
Autoptimize <= 3.1.13 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2025-13401
Affected versions- All versions up to and including 3.1.13
Patched versions: 3.1.14
Update to at least version 3.1.14.
Autoptimize <= 3.1.6 - Authenticated (Admin+) Stored Cross-Site Scripting via Critical CSS Rules
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.4)
- CVE:
- CVE-2023-2113
Affected versions- All versions up to and including 3.1.6
Patched versions: 3.1.7
Update to at least version 3.1.7.
Autoptimize <= 3.0.4 - Sensitive Information Disclosure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2022-4057
Affected versions- All versions up to and including 3.0.4
Patched versions: 3.1.0
Update to at least version 3.1.0.
Autoptimize <= 3.1.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Critical CSS Settings
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.5)
- CVE:
- CVE-2022-2635
Affected versions- All versions up to and including 3.1.0
Patched versions: 3.1.1
Update to at least version 3.1.1.
Autoptimize <= 2.8.3 - Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.5)
- CVE:
- CVE-2021-24332
Affected versions- All versions before 2.8.4
Patched versions: 2.8.4
Update to at least version 2.8.4.
Autoptimize <= 2.7.7 - Arbitrary File Upload (and Remote Code Execution) via Import Settings
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2021-24376
Affected versions- All versions before 2.7.8
Patched versions: 2.7.8
Update to at least version 2.7.8.
Autoptimize <= 2.7.7 - Unsafe File Upload to Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.8)
- CVE:
- CVE-2021-24378
Affected versions- All versions before 2.7.8
Patched versions: 2.7.8
Update to at least version 2.7.8.
Autoptimize <= 2.7.7 - Race Condition leading to Remote Code Execution
- Published:
- Last updated:
- Severity:
- High (CVSS 8.1)
- CVE:
- CVE-2021-24377
Affected versions- All versions before 2.7.8
Patched versions: 2.7.8
Update to at least version 2.7.8.
Autoptimize <= 2.7.6 - Authenticated Arbitrary File Upload
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2020-24948
Affected versions- All versions up to and including 2.7.6
Patched versions: 2.7.7
Update to at least version 2.7.7.
Autoptimize <= 2.1.0 - Unauthenticated Local File Inclusion
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
Affected versions- All versions up to and including 2.1.0
Patched versions: 2.1.1
Update to at least version 2.1.1.
Check Autoptimize on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What Autoptimize rewrites, and who supplies the input
By the FAQ on its wordpress.org listing, the CSS and JS files Autoptimize builds sit under /wp-content/cache/autoptimize/ by default, and links to them are stored in each page's HTML.
Two routes for input can be read from the dashboard.
One is the settings screen, which the listing places at Settings > Autoptimize. The plugin's text for it has free-text boxes for script and CSS exclusions, a CDN Base URL and pasted above the fold CSS, and its Extra tab takes third-party domains to preconnect to and full URLs to preload. WordPress documents the Administrator as having access to all administration features within a single site.
The other is the post editor. A Misc option labelled "Enable configuration per post/ page?" adds, in its own words, a "meta box" to the post/ page edit screen, and that box has a field labelled "LCP Image to preload". WordPress documents a Contributor as able to write and manage its own posts, so record who sees that box.
Autoptimize vulnerabilities on record, and the titles that need care
Stored Cross-Site Scripting recurs across the titles in this history, and file upload appears in more than one.
Access wording differs: titles read Unauthenticated, Authenticated (Contributor+), Authenticated (Admin+) or Authenticated with no role named, and some give no access wording. Two examples:
- CVE-2026-14995 has a title ending Unauthenticated Stored Cross-Site Scripting via REQUEST_URI Path. Affected range: all versions up to and including 3.1.15.1. Patched versions field: 3.1.16.
- CVE-2026-2352 has a title ending Authenticated (Contributor+) Stored Cross-Site Scripting via 'ao_post_preload' Meta Value. Affected range: all versions up to and including 3.1.14. Patched versions field: 3.1.15.
A title that names no plugin, and a record with no CVE id
CVE-2026-3220 has a title that reads Multiple Plugins <= Multiple Versions - Unauthenticated Stored Cross-Site Scripting, naming neither this plugin nor a version. Match on its fields: the affected range is all versions before 3.1.15, and the patched versions field lists 3.1.15.
A record with no CVE id has a title ending Unauthenticated Local File Inclusion. Its affected range is all versions up to and including 2.1.0 and its patched versions field lists 2.1.1.
The changelog on the plugin's wordpress.org listing is a second place to read before relying on the update guidance at the top of the history: it is the developer's release notes, some of its entries have lines that begin with the word "security", and a release it describes may have no record on this page.
Autoptimize security checks, and where each setting is read
Each check reads and changes nothing.
The tabs at Settings > Autoptimize used here are named, in the plugin's text, JS, CSS & HTML, Images and Extra. The main tab ends in two buttons, Save Changes and Save Changes and Empty Cache, and the Extra tab may carry links reading "Click here to install and activate it." Press none.
The WordPress Plugins screen gives each plugin's version number in its Description column. Write down Autoptimize's, the date, and what its Automatic update column shows. If the number is not one the listing's changelog names, note that too: the listing credits Plugin Update Checker "for automated updates from Github for the beta version".
Under JavaScript Options and under CSS Options, the first row is a tick box whose label is a single question about that kind of code, with no other text beside it: record both before the rows under them. Under JavaScript Options, record whether "Aggregate JS-files?", "Also aggregate inline JS?" and "Do not aggregate but defer?" are ticked.
Under CSS Options, record "Aggregate CSS-files?", "Also aggregate inline CSS?", "Inline all CSS?" and "Eliminate render-blocking CSS?", and copy the box beneath it, whose placeholder begins "Paste the above the fold CSS here." The listing's FAQ says that on new installations Autoptimize will not aggregate CSS and JS files any more, so note when the plugin was first installed and ask who ticked an aggregation box.
Copy the Cache Info rows: Cache folder, "Can we write?" and Cached styles and scripts. The FAQ lists a page requested with ?ao_noptimize=1 appended to the URL among those Autoptimize leaves alone. Loading one page both ways shows what it rewrites.
"Exclude scripts from Autoptimize:" and "Exclude CSS from Autoptimize:" each hold a comma-separated list. The FAQ calls the entries identifiers: part of a file's path, a plugin's folder, or a unique string from a block of inline code. Copy both lists, and record "Minify excluded CSS and JS files?" under Misc Options: its text says that when aggregating, excluded files that are not minified (based on filename) are by default minified despite being excluded.
The FAQ adds that starting with version 1.6.6 everything inside noptimize tags is excluded, in page or post content, in widgets and in theme files.
Record the two Misc tick boxes whose text begins "By default Autoptimize is also active": one covers logged-on editors/ administrators, the other a shop's cart/ checkout. Where "Enable configuration per post/ page?" is ticked, open an existing post's edit screen as each role you can sign in as and note whether a box titled "Autoptimize this page" appears.
Do this only on a staging copy: no vendor page cited here says what opening the edit screen does. Do not save the post or press its Generate Critical CSS button: the box's messages include "Added to CCSS job queue."
On the Images tab, find the tick box whose text mentions fast delivery "via the Shortpixel global CDN". The listing's FAQ says that with image optimisation on, Autoptimize looks for png, gif and jpeg files in image tags and in CSS files loaded from your own domain and changes their source to the ShortPixel CDN.
Record whether the box is ticked, the quality chosen and the first of the tab's two exclusion fields, a comma-separated list of image classes or filenames.
Then record "Lazy-load images?", "Lazy-load exclusions" and "Lazy-load from nth image". The tab's text may offer a link to refresh the quota status. Leave it.
The listing's FAQ speaks of a "Delete Cache" link in the Autoptimize dropdown in the admin toolbar and of a "Save changes & clear cache" button on the settings page. The toolbar text has an item labelled "Clear CSS/ JS Cache", and the settings text has a button labelled "Save Changes and Empty Cache".
Sign in as each role you can and write down whether the toolbar carries the Autoptimize menu, leaving its items alone. Then list the accounts under the Administrator filter link of the WordPress Users screen.
The FAQ says that as from AO 2.4 Autoptimize "listens" to page cache purges to clear its own cache, so write down which page cache the site runs and who may purge it.
What a version match does not show for Autoptimize
Finding the installed Autoptimize version inside an affected range tells you a record applies to that copy.
It does not tell you whether anyone used the flaw, or what the settings hold: the CSS pasted into the above the fold box, the domains and URLs on the Extra tab, or what a settings import brought in. The listing's changelog says the settings export and import on the critical CSS tab takes into account all Autoptimize settings.
The listing also describes an API of filters, among them ones that change the CSS and JS excludes. Read the theme's files and any helper plugin.
Titles in this history carry Contributor+ and Admin+ wording, and a WordPress security audit works role by role: it signs in as each role with test accounts, and among other checks it tests whether script an editor saves runs when an administrator opens the page.
Frequently asked questions
Each record answers in its affected range and patched versions field, and a title can give no version to go by: CVE-2026-3220 has a title that begins Multiple Plugins <= Multiple Versions, with an affected range of all versions before 3.1.15 and 3.1.15 in its patched versions field. CVE-2021-24376 covers all versions before 2.7.8 and lists 2.7.8. Set your installed version against every affected range in the history, then read the update guidance at the top of the history.
Take the installed version from the WordPress Plugins screen and set it beside the update guidance at the top of the history. Before relying on that guidance, read the changelog on the plugin's wordpress.org listing, where some entries have lines that begin with the word "security". If the installed number is not one that changelog names, note it: the listing credits Plugin Update Checker "for automated updates from Github for the beta version".
The records here are the ones the source data files under the autoptimize slug, and being filed there does not settle whether a record also applies to another product. The vendor's Pro page describes Autoptimize Pro as "a premium Power-Up that extends AO", sold as a subscription. The plugin's listing says the Critical CSS power-up is not needed with Autoptimize 2.7 or higher, because all of its functionality is now part of Autoptimize.
To the ShortPixel CDN, by the listing's FAQ: the feature depends on an external service fetching the original image from your site and saving it on the CDN, so it can only work for publicly available images. The Images tab's text says use of the feature is subject to Shortpixel's Terms of Use and Privacy policy. Record whether the box is ticked.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 14 of the 15 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Autoptimize <= 3.1.15.1 - Unauthenticated Stored Cross-Site Scripting via Comment Author Name (CVE-2026-78471)
- Autoptimize <= 3.1.15.1 - Unauthenticated Stored Cross-Site Scripting via REQUEST_URI Path (CVE-2026-14995)
- Multiple Plugins <= Multiple Versions - Unauthenticated Stored Cross-Site Scripting (CVE-2026-3220)
- Autoptimize <= 3.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'ao_post_preload' Meta Value (CVE-2026-2352)
- Autoptimize <= 3.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via Lazy-loaded Image Attributes (CVE-2026-2430)
- Autoptimize <= 3.1.13 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2025-13401)
- Autoptimize <= 3.1.6 - Authenticated (Admin+) Stored Cross-Site Scripting via Critical CSS Rules (CVE-2023-2113)
- Autoptimize <= 3.0.4 - Sensitive Information Disclosure (CVE-2022-4057)
- Autoptimize <= 3.1.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Critical CSS Settings (CVE-2022-2635)
- Autoptimize <= 2.8.3 - Stored Cross-Site Scripting (CVE-2021-24332)
- Autoptimize <= 2.7.7 - Arbitrary File Upload (and Remote Code Execution) via Import Settings (CVE-2021-24376)
- Autoptimize <= 2.7.7 - Unsafe File Upload to Cross-Site Scripting (CVE-2021-24378)
- Autoptimize <= 2.7.7 - Race Condition leading to Remote Code Execution (CVE-2021-24377)
- Autoptimize <= 2.7.6 - Authenticated Arbitrary File Upload (CVE-2020-24948)
- Autoptimize <= 2.1.0 - Unauthenticated Local File Inclusion