CVE-2026-7252 json
WP-Optimize <= 4.5.2 - Authenticated (Author+) Arbitrary File Deletion via 'original-file' Post Meta
published 2026-05-07 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-28323
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
The WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the unscheduled_original_file_deletion function in all versions up to, and including, 4.5.2 This makes it possible for authenticated attackers, with author-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). This is possible because 'original-file' is a public (non-protected) meta key — it does not begin with an underscore — allowing Authors to freely create or modify it on their own attachment posts via the standard Edit Media form or the REST API.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
Affected products
- davidanderson WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/cc815ef2-dd02-4faa-b202-dd1552f889db?source=cve
- plugins.trac.wordpress.org /browser/wp-optimize/trunk/includes/class-updraft-smush-manager.php#L1649
- plugins.trac.wordpress.org /browser/wp-optimize/tags/4.5.2/includes/class-updraft-smush-manager.php#L1649
- plugins.trac.wordpress.org /browser/wp-optimize/trunk/includes/class-updraft-smush-manager.php#L1645
- plugins.trac.wordpress.org /browser/wp-optimize/tags/4.5.2/includes/class-updraft-smush-manager.php#L1645
- plugins.trac.wordpress.org /browser/wp-optimize/trunk/includes/class-updraft-smush-manager.php#L81
- plugins.trac.wordpress.org /browser/wp-optimize/tags/4.5.2/includes/class-updraft-smush-manager.php#L81
- plugins.trac.wordpress.org /changeset/3518513/wp-optimize/trunk/includes/class-updraft-smush-manager.php
- plugins.trac.wordpress.org /changeset?old_path=%2Fwp-optimize/tags/4.5.2&new_path=%2Fwp-optimize/tags/4.5.3
Sources
- CVE List CVE-2026-7252
- NVD CVE-2026-7252
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.