LiveActive security incident?Get immediate response
CVE Record

CVE-2021-24376: Autoptimize < 2.7.8 - Arbitrary File Upload via "Import Settings"

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Autoptimize for WordPress before 2.7.8 could leave PHP files on disk when importing a crafted settings ZIP. If that file becomes executable by the web server, the issue can lead to remote code execution. No CVSS score or active exploitation evidence is provided in the bundle.

Executive priority

Treat as high priority for WordPress sites using Autoptimize, because successful exploitation may allow server-side code execution. Prioritize internet-facing and business-critical WordPress properties first.

Technical view

The plugin tried to remove malicious files after extracting an uploaded archive, but did not inspect extracted folders. A PHP file placed inside a directory could survive extraction cleanup, bypassing CVE-2020-24948 protections and enabling arbitrary file upload with potential RCE.

Likely exposure

Exposure is likely limited to WordPress installations running Autoptimize before 2.7.8 where the Import Settings function is reachable. The provided affected metadata is sparse and inconsistently lists 2.7.8, while the description says versions before 2.7.8.

Exploitation context

The bundle states this can achieve remote code execution through a crafted settings archive. It does not provide evidence of active exploitation, and KEV is false in the supplied data.

Researcher notes

The key weakness is CWE-434: unrestricted upload of dangerous file types. Source detail indicates cleanup occurred after extraction and missed nested PHP files. Authentication requirements, CVSS, and exploit-in-the-wild evidence are not established in the supplied bundle.

Mitigation direction

  • Update Autoptimize to version 2.7.8 or later.
  • Review vendor guidance and WPScan details for any additional remediation.
  • Restrict access to plugin settings import functionality.
  • Check web-accessible upload or cache paths for unexpected PHP files.

Validation and detection

  • Inventory WordPress sites using the Autoptimize plugin.
  • Confirm the installed Autoptimize version is 2.7.8 or later.
  • Review logs for suspicious settings import activity.
  • Inspect plugin-related directories for unexpected executable files.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-24376 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownAutoptimize2.7.8Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.