LiveActive security incident?Get immediate response
CVE Record

CVE-2021-24377: Autoptimize < 2.7.8 - Race Condition leading to RCE

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Autoptimize before 2.7.8 can briefly leave a dangerous uploaded file in place during settings import. An attacker who can reach that workflow may win a timing window and execute code on the WordPress server. The sources do not provide CVSS, prerequisites, or proof of active exploitation.

Executive priority

Treat as a priority for WordPress environments because the stated impact is remote code execution. Urgency is highest where many sites run Autoptimize or administrative access is broadly delegated. Evidence is incomplete, so remediation should focus on version verification and patching.

Technical view

This is a CWE-362 race condition in Autoptimize’s Import Settings archive extraction and cleanup logic. The plugin attempted to remove malicious files after extraction, but a timing gap before removal could permit remote code execution. The record describes it as a bypass of CVE-2020-24948.

Likely exposure

Exposure is likely limited to WordPress sites running Autoptimize versions before 2.7.8, especially where the Import Settings feature is accessible. The supplied sources do not define required user privileges, hosting configurations, or affected WordPress versions.

Exploitation context

The bundle does not cite KEV inclusion or any source confirming active exploitation. Exploitation depends on a race window during archive import; the sources do not provide reliable evidence about exploit availability, attacker access requirements, or observed attacks.

Researcher notes

The key technical issue is cleanup after extraction rather than prevention before exposure. The record names CVE-2020-24948 bypass behavior, but the bundle provides no CVSS vector, exploit chain detail, privilege requirement, or fixed-code analysis.

Mitigation direction

  • Update Autoptimize to version 2.7.8 or later.
  • Disable or remove Autoptimize if prompt updating is not possible.
  • Restrict access to WordPress administration and settings import workflows.
  • Check WPScan and vendor guidance for any additional remediation notes.

Validation and detection

  • Inventory WordPress sites for Autoptimize plugin version below 2.7.8.
  • Confirm the Import Settings feature is not exposed to untrusted users.
  • Review server logs for suspicious file creation or access near import activity.
  • Verify patched sites report Autoptimize 2.7.8 or later.
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 · low confidence lookup

CWE-362: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2021-24377 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-362 · source CWE mapping

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.