HomeWordPress vulnerabilitiesAutoptimize
Autoptimize vulnerabilities
Autoptimize has 13 known vulnerabilities in this database. The most recent published record is dated 2 Oct 2026.
- Known vulnerabilities
- 13
- Active installs
- 800,000+
- Latest version
- 3.1.16
- Last updated
- 26 Sep 2026
- Most recent
- 2 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-78471 | Medium 5.4 | Up to 3.1.15.1 | Fixed in a later version (latest 3.1.16) | 5 d ago |
| Cross-site scripting (XSS) CVE-2026-14995 | High 7.2 | Up to 3.1.15.1 | Fixed in a later version (latest 3.1.16) | 6 d ago |
| Cross-site scripting (XSS) CVE-2026-3220 | High 8.8 | Before 3.1.15 | Fixed in 3.1.15 | 18 May 2026 |
| Cross-site scripting (XSS) CVE-2026-2430 | Medium 6.4 | Up to 3.1.14 | Fixed in a later version (latest 3.1.16) | 21 Mar 2026 |
| Cross-site scripting (XSS) CVE-2026-2352 | Medium 6.4 | Up to 3.1.14 | Fixed in a later version (latest 3.1.16) | 21 Mar 2026 |
| Cross-site scripting (XSS) CVE-2025-13401 | Medium 6.4 | Up to 3.1.13 | Fixed in a later version (latest 3.1.16) | 3 Dec 2025 |
| Security weakness CVE-2023-2113 | Medium 4.8 | Before 3.1.7 | Fixed in 3.1.7 | 30 May 2023 |
| Security weakness CVE-2022-4057 | Medium 5.3 | Before 3.1.0 | Fixed in 3.1.0 | 2 Jan 2023 |
| Cross-site scripting (XSS) CVE-2022-2635 | Medium 4.8 | Before 3.1.1 | Fixed in 3.1.1 | 16 Sep 2022 |
| Remote code execution CVE-2021-24376 | Critical 9.8 | Before 2.7.8 | Fixed in 2.7.8 | 21 Jun 2021 |
| Remote code execution CVE-2021-24377 | High 8.1 | Before 2.7.8 | Fixed in 2.7.8 | 21 Jun 2021 |
| Cross-site scripting (XSS) CVE-2021-24378 | Medium 4.8 | Before 2.7.8 | Fixed in 2.7.8 | 21 Jun 2021 |
| Cross-site scripting (XSS) CVE-2021-24332 | Medium 4.8 | Before 2.8.4 | Fixed in 2.8.4 | 24 May 2021 |
Read the published descriptions
- CVE-2026-78471, 2 Oct 2026
- The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name 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 an administrator to have enabled Autoptimize's 'Lazy-load images?' option, the w3-total-cache/w3-total-cache.php file to be present on disk with the plugin disabled, a class named Minify_HTML to be loaded into scope by another plugin, and the malicious comment to be approved by a moderator before the payload renders. CVE record
- CVE-2026-14995, 1 Oct 2026
- 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(). CVE record
- CVE-2026-3220, 18 May 2026
- The Autoptimize WordPress plugin before 3.1.15, Clearfy Cache WordPress plugin before 2.4.2, Speed Optimizer WordPress plugin before 7.7.9 are vulnerable to unauthenticated Stored Cross-Site Scripting (XSS) due to a predictable replacement hash used during the HTML minification process and abusing a regular expression. This allows an attacker to inject arbitrary HTML attributes in the final HTML output by anticipating the placeholder format. CVE record
- CVE-2026-2430, 21 Mar 2026
- The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the lazy-loading image processing in all versions up to, and including, 3.1.14. This is due to the use of an overly permissive regular expression in the `add_lazyload` function that replaces all occurrences of `\ssrc=` in image tags without limiting to the actual attribute. 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 by crafting an image tag where the `src` URL contains a space followed by `src=`, causing the regex to break the HTML structure and promote text inside attribute values into executable HTML attributes. CVE record
- CVE-2026-2352, 21 Mar 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 `ao_metabox_save()` function and missing output escaping when the value is rendered into a `<link>` tag in `autoptimizeImages.php`. 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. CVE record
- CVE-2025-13401, 3 Dec 2025
- The Autoptimize plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the LCP Image to preload metabox in all versions up to, and including, 3.1.13 due to insufficient input sanitization and output escaping on user-supplied image attributes in the "create_img_preload_tag" function. 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. CVE record
- CVE-2023-2113, 30 May 2023
- The Autoptimize WordPress plugin before 3.1.7 does not sanitise and escape the settings imported from a previous export, allowing high privileged users (such as an administrator) to inject arbitrary javascript into the admin panel, even when the unfiltered_html capability is disabled, such as in a multisite setup. CVE record
- CVE-2022-4057, 2 Jan 2023
- The Autoptimize WordPress plugin before 3.1.0 uses an easily guessable path to store plugin's exported settings and logs. CVE record
- CVE-2022-2635, 16 Sep 2022
- The Autoptimize WordPress plugin before 3.1.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2021-24376, 21 Jun 2021
- The Autoptimize WordPress plugin before 2.7.8 attempts to delete malicious files (such as .php) form the uploaded archive via the "Import Settings" feature, after its extraction. However, the extracted folders are not checked and it is possible to upload a zip which contained a directory with PHP file in it and then it is not removed from the disk. It is a bypass of CVE-2020-24948 which allows sending a PHP file via the "Import Settings" functionality to achieve Remote Code Execution. CVE record
- CVE-2021-24377, 21 Jun 2021
- The Autoptimize WordPress plugin before 2.7.8 attempts to remove potential malicious files from the extracted archive uploaded via the 'Import Settings' feature, however this is not sufficient to protect against RCE as a race condition can be achieved in between the moment the file is extracted on the disk but not yet removed. It is a bypass of CVE-2020-24948. CVE record
- CVE-2021-24378, 21 Jun 2021
- The Autoptimize WordPress plugin before 2.7.8 does not check for malicious files such as .html in the archive uploaded via the 'Import Settings' feature. As a result, it is possible for a high privilege user to upload a malicious file containing JavaScript code inside an archive which will execute when a victim visits index.html inside the plugin directory. CVE record
- CVE-2021-24332, 24 May 2021
- The Autoptimize WordPress plugin before 2.8.4 was missing proper escaping and sanitisation in some of its settings, allowing high privilege users to set XSS payloads in them, leading to stored Cross-Site Scripting issues CVE record
What to do if you run Autoptimize
If you run Autoptimize, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Autoptimize vulnerabilities
Free. We email you when a new vulnerability is published for Autoptimize, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.