The Autoptimize plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2.1.0. This allows unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. This requires both JS and CSS aggregation, and the 'Also aggregate inline CSS' option to be set.
This vulnerability is a critical severity with CVSS 9.8 Local File Inclusion issue affecting the Plugin Autoptimize. It affects Versions up to 2.1.0 and is fixed in 2.1.1.
Use the related hub and response guides to connect this vulnerability report with patch validation, scanner checks, and site hardening work.
Open the grouped hub for related CVEs, affected ranges, severity mix, and patch coverage.
Check access, XML-RPC exposure, backup readiness, and monitoring after patching.
Use containment, evidence capture, remediation, and validation steps when exploit risk is high.
the tracked vulnerability is tracked for the Plugin Autoptimize as critical severity with CVSS 9.8. The affected range is Versions up to 2.1.0. Update Autoptimize to 2.1.1 or newer where that version is compatible with the site.
Search engines and operators need more than a title. This page exposes the identifier, affected range, patch evidence, and source coverage that make the vulnerability actionable.
This report uses the upstream feed identifier because a CVE has not been attached to the record yet.
Affected version data gives operators a concrete comparison point against installed WordPress software.
A fixed version is present, so the page can answer update and remediation intent directly.
External references are available for source validation, advisory review, and incident notes.
Use these checks when converting this record into a patch ticket, incident note, or risk acceptance decision.
Inventory the installed Plugin package and compare its version with Versions up to 2.1.0.
Confirm Autoptimize is updated to 2.1.1 or newer.
Review references and CVSS vector details for exploitability, authentication requirements, and exposure path.
After patching, re-run vulnerability monitoring and keep the related plugin or theme hub under review for follow-up CVEs.
| Software Type | Plugin |
|---|---|
| Software Slug |
autoptimize
View on wordpress.org
|
| CVE | No linked CVE entry. |
| Patched Versions |
2.1.1
|
| Affected Versions |
Versions up to 2.1.0
|
These internal links group the same WordPress plugin by CVE, issue type, severity, and patch status so operators and search engines can connect the full vulnerability cluster.
Autoptimize <= 2.7.7 - Arbitrary File Upload (and Remote Code Execution) via Import Settings
Autoptimize <= 2.7.7 - Race Condition leading to Remote Code Execution
Autoptimize <= 2.7.6 - Authenticated Arbitrary File Upload
Autoptimize <= 3.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via Lazy-loaded Image Attributes
Autoptimize <= 3.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'ao_post_preload' Meta Value
Autoptimize <= 3.1.13 - Authenticated (Contributor+) Stored Cross-Site Scripting
Autoptimize <= 3.1.0 - Authenticated (Admin+) Stored Cross-Site Scripting via Critical CSS Settings
Autoptimize <= 2.8.3 - Stored Cross-Site Scripting
This record contains material that is subject to copyright
License: 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. Read more
