Skip to main content
WordPress plugin recordReviewed

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.

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.

  1. Autoptimize <= 3.1.15.1 - Unauthenticated Stored Cross-Site Scripting via Comment Author Name

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    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.

  2. Autoptimize <= 3.1.15.1 - Unauthenticated Stored Cross-Site Scripting via REQUEST_URI Path

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    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.

  3. Multiple Plugins <= Multiple Versions - Unauthenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions before 3.1.15

    Patched versions: 3.1.15

    Update to at least version 3.1.15.

  4. Autoptimize <= 3.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'ao_post_preload' Meta Value

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 3.1.14

    Patched versions: 3.1.15

    Update to at least version 3.1.15.

  5. Autoptimize <= 3.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via Lazy-loaded Image Attributes

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    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 records
  1. Autoptimize <= 3.1.13 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 3.1.13

    Patched versions: 3.1.14

    Update to at least version 3.1.14.

  2. Autoptimize <= 3.1.6 - Authenticated (Admin+) Stored Cross-Site Scripting via Critical CSS Rules

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.4)
    Affected versions
    • All versions up to and including 3.1.6

    Patched versions: 3.1.7

    Update to at least version 3.1.7.

  3. Autoptimize <= 3.0.4 - Sensitive Information Disclosure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 3.0.4

    Patched versions: 3.1.0

    Update to at least version 3.1.0.

  4. Autoptimize <= 3.1.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Critical CSS Settings

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions up to and including 3.1.0

    Patched versions: 3.1.1

    Update to at least version 3.1.1.

  5. Autoptimize <= 2.8.3 - Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions before 2.8.4

    Patched versions: 2.8.4

    Update to at least version 2.8.4.

  6. Autoptimize <= 2.7.7 - Arbitrary File Upload (and Remote Code Execution) via Import Settings

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions before 2.7.8

    Patched versions: 2.7.8

    Update to at least version 2.7.8.

  7. Autoptimize <= 2.7.7 - Unsafe File Upload to Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.8)
    Affected versions
    • All versions before 2.7.8

    Patched versions: 2.7.8

    Update to at least version 2.7.8.

  8. Autoptimize <= 2.7.7 - Race Condition leading to Remote Code Execution

    Published:
    Last updated:
    Severity:
    High (CVSS 8.1)
    Affected versions
    • All versions before 2.7.8

    Patched versions: 2.7.8

    Update to at least version 2.7.8.

  9. Autoptimize <= 2.7.6 - Authenticated Arbitrary File Upload

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 2.7.6

    Patched versions: 2.7.7

    Update to at least version 2.7.7.

  10. 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.

Installed version

The WordPress Plugins screen gives each plugin's version number in its Description column. 1 min read

Script and style aggregation

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. 1 min read

Exclusion lists

"Exclude scripts from Autoptimize:" and "Exclude CSS from Autoptimize:" each hold a comma-separated list. 1 min read

Image settings

On the Images tab, find the tick box whose text mentions fast delivery "via the Shortpixel global CDN". 1 min read

Who can clear the cache

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. 1 min read

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 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.