CVE-2026-84221

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory published 2026-09-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

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

The Kirki WordPress plugin before 6.3.0 does not escape a user-supplied identifier before using it in a SQL query, allowing users with editor-level access and above to append arbitrary SQL and read the contents of the database, including user credentials.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

September 5, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 6, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Kirki 6.0.0 – 6.2.5 – Editor+ SQLi via Content Manager Field ID | CVE 2026-84221 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/6c34da62-46fb-4dd4-a433-bd3df4d9fcfd/

Vendor Advisories for CVE-2026-84221(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 19× in last 7d / 58× 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.

  1. 2026-09-24 18:23 UTCEG score recompute
  2. 2026-09-24 18:23 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 17:56 UTCEG score recompute
  5. 2026-09-23 17:56 UTCGHSA enrichment
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-22 18:21 UTCEG score recompute
  8. 2026-09-22 18:21 UTCGHSA enrichment
  9. 2026-09-22 16:01 UTCEPSS rescore
  10. 2026-09-21 21:09 UTCEPSS rescore
  11. 2026-09-21 18:45 UTCEG score recompute
  12. 2026-09-21 18:45 UTCGHSA enrichment
  13. 2026-09-20 20:16 UTCEPSS rescore
  14. 2026-09-20 19:09 UTCGHSA enrichment
  15. 2026-09-19 19:33 UTCEG score recompute
  16. 2026-09-19 19:33 UTCGHSA enrichment
  17. 2026-09-18 19:58 UTCEG score recompute
  18. 2026-09-18 19:58 UTCGHSA enrichment
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-17 20:22 UTCEG score recompute
  21. 2026-09-17 20:22 UTCGHSA enrichment
  22. 2026-09-17 19:32 UTCEPSS rescore
  23. 2026-09-16 18:21 UTCEG score recompute
  24. 2026-09-16 18:21 UTCGHSA enrichment
  25. 2026-09-16 14:09 UTCEPSS rescore
Show 33 more
  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-15 18:18 UTCEG score recompute
  3. 2026-09-15 18:18 UTCGHSA enrichment
  4. 2026-09-15 03:12 UTCEPSS rescore
  5. 2026-09-15 03:12 UTCEPSS rescore
  6. 2026-09-14 18:22 UTCGHSA enrichment
  7. 2026-09-13 17:57 UTCEG score recompute
  8. 2026-09-13 17:57 UTCGHSA enrichment
  9. 2026-09-12 18:21 UTCEG score recompute
  10. 2026-09-12 18:21 UTCGHSA enrichment
  11. 2026-09-11 18:45 UTCEG score recompute
  12. 2026-09-11 18:45 UTCGHSA enrichment
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 19:09 UTCEG score recompute
  16. 2026-09-10 19:09 UTCGHSA enrichment
  17. 2026-09-09 19:33 UTCEG score recompute
  18. 2026-09-09 19:33 UTCGHSA enrichment
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-08 19:55 UTCGHSA enrichment
  21. 2026-09-08 10:44 UTCEG score recompute
  22. 2026-09-08 10:44 UTCGHSA enrichment
  23. 2026-09-07 11:00 UTCEG score recompute
  24. 2026-09-07 11:00 UTCGHSA enrichment
  25. 2026-09-06 13:48 UTCEPSS rescore
  26. 2026-09-06 11:22 UTCGHSA enrichment
  27. 2026-09-06 10:45 UTCEG score recompute▲ 6.80
  28. 2026-09-06 10:45 UTCGHSA enrichment
  29. 2026-09-06 10:44 UTCMITRE cvelistV5CVSS v3 → 6.8 · severity → MEDIUM
  30. 2026-09-05 15:31 UTCEPSS rescore
  31. 2026-09-05 07:23 UTCNVD update
  32. 2026-09-05 06:35 UTCEG score recompute
  33. 2026-09-05 06:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84221?
CVE-2026-84221 is a medium vulnerability published on September 5, 2026. The Kirki WordPress plugin before 6.3.0 does not escape a user-supplied identifier before using it in a SQL query, allowing users with editor-level access and above to append arbitrary SQL and read the contents of the database, including user credentials.
When was CVE-2026-84221 disclosed?
CVE-2026-84221 was first published in the National Vulnerability Database on September 5, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84221 actively exploited?
CVE-2026-84221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.9% of all scored CVEs.
What is the CVSS score of CVE-2026-84221?
CVE-2026-84221 has a CVSS v3.1 base score of 6.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-84221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84221, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-84221?

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

Book a Demo →Browse All CVEs