CVE-2026-5821

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The Image Optimizer plugin for WordPress is vulnerable to arbitrary file deletion in versions up to and including 1.7.4. This is due to insufficient path validation in the Image_Backup::remove() function where backup file paths stored in post meta are used directly in file deletion operations without verifying they are within the uploads directory. The plugin stores backup file paths in the image_optimizer_metadata post meta field and trusts these paths completely when deleting backups on the delete_attachment hook. An authenticated attacker with Author-level access can edit the image_optimizer_metadata post meta on their own attachments via WordPress's Custom Fields interface, injecting arbitrary absolute file paths into the backups array. When the attacker subsequently deletes the attachment, the plugin calls File_System::delete() on each path without validation. This makes it possible for authenticated attackers, with Author-level access and above, to delete arbitrary files on the server within the web server's filesystem permissions, potentially leading to denial of service, data loss, or security degradation.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

Published

July 2, 2026

Last Modified

July 2, 2026

References (8)

Vendor Advisories for CVE-2026-5821(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 249 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-24 14:04 UTCEPSS rescore
  14. 2026-09-23 17:54 UTCEPSS rescore
  15. 2026-09-23 06:43 UTCEG score recompute
  16. 2026-09-23 06:43 UTCGHSA enrichment
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 06:23 UTCEG score recompute
  20. 2026-09-18 06:22 UTCGHSA enrichment
  21. 2026-09-17 19:31 UTCEPSS rescore
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-15 03:11 UTCEPSS rescore
  25. 2026-09-14 00:18 UTCEG score recompute
Show 75 more
  1. 2026-09-14 00:18 UTCGHSA enrichment
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-13 09:03 UTCEG score recompute
  4. 2026-09-13 09:03 UTCGHSA enrichment
  5. 2026-09-12 14:32 UTCEG score recompute
  6. 2026-09-12 14:32 UTCGHSA enrichment
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 09:35 UTCEPSS rescore
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 14:23 UTCEG score recompute
  12. 2026-09-06 14:23 UTCGHSA enrichment
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 00:33 UTCEG score recompute
  15. 2026-09-06 00:33 UTCGHSA enrichment
  16. 2026-09-04 05:07 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 13:54 UTCEPSS rescore
  19. 2026-09-01 04:40 UTCEPSS rescore
  20. 2026-08-30 22:35 UTCEG score recompute
  21. 2026-08-30 22:35 UTCGHSA enrichment
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 11:26 UTCEG score recompute
  24. 2026-08-30 11:26 UTCGHSA enrichment
  25. 2026-08-30 01:22 UTCEPSS rescore
  26. 2026-08-28 21:42 UTCEPSS rescore
  27. 2026-08-27 22:20 UTCEG score recompute
  28. 2026-08-27 22:20 UTCGHSA enrichment
  29. 2026-08-27 14:25 UTCEPSS rescore
  30. 2026-08-26 14:46 UTCEPSS rescore
  31. 2026-08-25 16:04 UTCEG score recompute
  32. 2026-08-25 16:04 UTCGHSA enrichment
  33. 2026-08-25 13:49 UTCEPSS rescore
  34. 2026-08-24 20:57 UTCEG score recompute
  35. 2026-08-24 20:57 UTCGHSA enrichment
  36. 2026-08-24 05:17 UTCGHSA enrichment
  37. 2026-08-23 18:07 UTCGHSA enrichment
  38. 2026-08-23 06:58 UTCEG score recompute
  39. 2026-08-23 06:58 UTCGHSA enrichment
  40. 2026-08-23 00:19 UTCEPSS rescore
  41. 2026-08-22 19:45 UTCGHSA enrichment
  42. 2026-08-22 06:45 UTCEG score recompute
  43. 2026-08-22 06:45 UTCGHSA enrichment
  44. 2026-08-21 23:49 UTCEPSS rescore
  45. 2026-08-21 15:48 UTCGHSA enrichment
  46. 2026-08-21 04:29 UTCEG score recompute
  47. 2026-08-21 04:29 UTCGHSA enrichment
  48. 2026-08-20 22:55 UTCEPSS rescore
  49. 2026-08-20 15:53 UTCGHSA enrichment
  50. 2026-08-20 04:24 UTCEG score recompute
  51. 2026-08-20 04:24 UTCGHSA enrichment
  52. 2026-08-19 17:04 UTCEPSS rescore
  53. 2026-08-19 10:18 UTCGHSA enrichment
  54. 2026-08-18 23:03 UTCEG score recompute
  55. 2026-08-18 23:02 UTCGHSA enrichment
  56. 2026-08-18 13:48 UTCEPSS rescore
  57. 2026-08-18 11:52 UTCGHSA enrichment
  58. 2026-08-17 22:58 UTCEG score recompute
  59. 2026-08-17 22:58 UTCGHSA enrichment
  60. 2026-08-17 13:47 UTCEPSS rescore
  61. 2026-08-17 07:25 UTCGHSA enrichment
  62. 2026-08-16 20:16 UTCEG score recompute
  63. 2026-08-16 20:16 UTCGHSA enrichment
  64. 2026-08-16 14:56 UTCEPSS rescore
  65. 2026-08-16 09:06 UTCEG score recompute
  66. 2026-08-16 09:06 UTCGHSA enrichment
  67. 2026-08-15 21:57 UTCGHSA enrichment
  68. 2026-08-15 10:47 UTCEG score recompute
  69. 2026-08-15 10:47 UTCGHSA enrichment
  70. 2026-08-15 01:30 UTCEPSS rescore
  71. 2026-08-14 23:37 UTCGHSA enrichment
  72. 2026-08-14 12:28 UTCGHSA enrichment
  73. 2026-08-14 01:18 UTCEG score recompute
  74. 2026-08-14 01:18 UTCGHSA enrichment
  75. 2026-08-13 22:00 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-5821?
CVE-2026-5821 is a high vulnerability published on July 2, 2026. The Image Optimizer plugin for WordPress is vulnerable to arbitrary file deletion in versions up to and including 1.7.4. This is due to insufficient path validation in the ImageBackup::remove() function where backup file paths stored in post meta are used directly in file deletion operations…
When was CVE-2026-5821 disclosed?
CVE-2026-5821 was first published on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5821 actively exploited?
CVE-2026-5821 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5821?
CVE-2026-5821 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-5821?
No fix for CVE-2026-5821 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-5821 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-5821

Explore →

Is Your Infrastructure Affected by CVE-2026-5821?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs