CVE-2026-3220

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-18. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (WPScan) lists Autoptimize versions before 3.1.15; Clearfy Cache versions before 2.4.2; Speed Optimizer versions before 7.7.9 as affected. No release containing a fix is confirmed on record.

The Autoptimize WordPress plugin before 3.1.15, Clearfy Cache WordPress plugin before 2.4.2, Speed Optimizer WordPress plugin before 7.7.9 are vulnerable to unauthenticated Stored Cross-Site Scripting (XSS) due to a predictable replacement hash used during the HTML minification process and abusing a regular expression. This allows an attacker to inject arbitrary HTML attributes in the final HTML output by anticipating the placeholder format.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 18, 2026

Last Modified

May 18, 2026

Advisory Details (1)

Auto-updated May 18, 2026
No fix on record yet.
Web page

Multiple Plugins – Unauthenticated Stored XSS via Minify Library | CVE 2026-3220 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/3ceabf11-23cd-4c38-ba14-014348b0ff2d/

Vendor Advisories for CVE-2026-3220(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 11× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 250 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 151 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-3220?
CVE-2026-3220 is a high-severity vulnerability; its CVE record was published on May 18, 2026. The Autoptimize WordPress plugin before 3.1.15, Clearfy Cache WordPress plugin before 2.4.2, Speed Optimizer WordPress plugin before 7.7.9 are vulnerable to unauthenticated Stored Cross-Site Scripting (XSS) due to a predictable replacement hash used during the HTML minification process and abusing…
When was the CVE record for CVE-2026-3220 published?
The CVE record for CVE-2026-3220 was published on May 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 18, 2026; the record at its source may have been updated since.
Is CVE-2026-3220 actively exploited?
CVE-2026-3220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3220?
CVE-2026-3220 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-3220?
No fix for CVE-2026-3220 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 CVE record's CNA (WPScan) lists Autoptimize versions before 3.1.15; Clearfy Cache versions before 2.4.2; Speed Optimizer versions before 7.7.9 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-3220 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-3220?

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

Book a Demo →Browse All CVEs