CVE-2026-54002

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.5Exploit: None knownExposed: 0

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

Kirby is an open-source content management system. Prior to 4.9.4 and 5.4.4, Kirby sites and plugins that use the writer or list fields or call Dom::sanitize(), Sane::sanitize(), Sane::Html::sanitize(), Sane::Svg::sanitize(), Sane::Xml::sanitize(), Sane::sanitizeFile(), or file sanitizeContents() with untrusted input allow malicious markup injected as children of an unknown HTML or XML tag to pass through Dom::sanitize() without being correctly sanitized, causing stored cross-site scripting. This issue is fixed in versions 4.9.4 and 5.4.4.

CVSS v3
8.5
EG Score
8.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity85% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

June 18, 2026

Last Modified

July 10, 2026

Advisory Details (7)

Auto-updated Jul 9, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Cross-site scripting (XSS) from incomplete HTML/XML sanitization in `Dom::sanitize()` · Advisory · getkirby/kirby · GitHub

https://github.com/getkirby/kirby/security/advisories/GHSA-wr9h-4r83-f4v6
github_release Patch Available

5.4.4

Patch available: getkirby/kirby 5.4.4

https://github.com/getkirby/kirby/releases/tag/5.4.4
github_release Patch Available

4.9.4

Patch available: getkirby/kirby 4.9.4

https://github.com/getkirby/kirby/releases/tag/4.9.4
github_commit Patch Available

commit bb2562e16c75 (getkirby/kirby)

Patch available: getkirby/kirby 5.4.4 (contains commit bb2562e16c75)

https://github.com/getkirby/kirby/commit/bb2562e16c754493a403b8df84c9883108871e4c
github_commit Patch Available

commit 9ec187386444 (getkirby/kirby)

Patch available: getkirby/kirby 5.4.4 (contains commit 9ec187386444)

https://github.com/getkirby/kirby/commit/9ec1873864441dbc06479ef7823da348ec7f2700
github_commit Patch Available

commit 7ad76cf9c738 (getkirby/kirby)

Patch available: getkirby/kirby 4.9.4 (contains commit 7ad76cf9c738)

https://github.com/getkirby/kirby/commit/7ad76cf9c7387462828e6ebfc8404e31b37829e9
github_commit Patch Available

commit 0f0437b5128c (getkirby/kirby)

Patch available: getkirby/kirby 4.9.4 (contains commit 0f0437b5128c)

https://github.com/getkirby/kirby/commit/0f0437b5128c910103cbc78fc34d94b2a3faef4c

Vendor Advisories for CVE-2026-54002(1)

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

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
getkirby/cms5.0.0 ... 5.4.3 (41 versions)5.4.4

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 50× 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-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 15:15 UTCEG score recompute
  3. 2026-08-23 01:13 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 06:33 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 08:09 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 07:59 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 01:28 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 03:04 UTCEG score recompute
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 04:41 UTCEG score recompute
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 06:14 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 18:09 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 19:42 UTCEG score recompute
  24. 2026-08-11 08:31 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 50 more
  1. 2026-08-09 22:56 UTCEG score recompute
  2. 2026-08-09 13:46 UTCEPSS rescore
  3. 2026-08-09 00:30 UTCEG score recompute
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-08 02:06 UTCEG score recompute
  6. 2026-08-06 16:30 UTCEG score recompute
  7. 2026-08-06 13:47 UTCEPSS rescore
  8. 2026-08-06 05:18 UTCEG score recompute
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-04 15:23 UTCEG score recompute
  11. 2026-08-04 15:10 UTCEPSS rescore
  12. 2026-08-04 10:39 UTCEPSS rescore
  13. 2026-08-03 19:56 UTCEG score recompute
  14. 2026-08-03 10:36 UTCEPSS rescore
  15. 2026-08-02 07:02 UTCEG score recompute
  16. 2026-08-02 02:27 UTCEPSS rescore
  17. 2026-08-01 08:38 UTCEG score recompute
  18. 2026-08-01 04:16 UTCEPSS rescore
  19. 2026-07-30 22:29 UTCEG score recompute
  20. 2026-07-30 16:28 UTCEPSS rescore
  21. 2026-07-30 03:09 UTCEG score recompute
  22. 2026-07-30 01:30 UTCEPSS rescore
  23. 2026-07-29 01:46 UTCEG score recompute
  24. 2026-07-28 15:37 UTCEPSS rescore
  25. 2026-07-27 18:12 UTCEG score recompute
  26. 2026-07-26 17:43 UTCEG score recompute
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-25 14:18 UTCEPSS rescore
  29. 2026-07-24 14:18 UTCEPSS rescore
  30. 2026-07-23 14:18 UTCEPSS rescore
  31. 2026-07-23 03:19 UTCEG score recompute
  32. 2026-07-22 14:08 UTCEPSS rescore
  33. 2026-07-21 15:25 UTCEPSS rescore
  34. 2026-07-20 17:08 UTCEPSS rescore
  35. 2026-07-19 02:29 UTCEPSS rescore
  36. 2026-07-18 10:04 UTCEPSS rescore
  37. 2026-07-16 17:03 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 16:57 UTCEPSS rescore
  40. 2026-07-15 02:00 UTCEPSS rescore
  41. 2026-07-15 02:00 UTCEPSS rescore
  42. 2026-07-13 22:31 UTCEPSS rescore
  43. 2026-07-13 06:13 UTCEPSS rescore
  44. 2026-07-13 06:13 UTCEPSS rescore
  45. 2026-07-12 05:46 UTCEPSS rescore
  46. 2026-07-11 08:27 UTCEPSS rescore
  47. 2026-07-11 08:27 UTCEPSS rescore
  48. 2026-07-09 19:14 UTCEG score recompute 8.50
  49. 2026-07-09 19:12 UTCMITRE cvelistV5CVSS v3 → 8.5 · CVSS v4 → 8.5
  50. 2026-06-18 15:08 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54002?
CVE-2026-54002 is a high vulnerability published on June 18, 2026. Kirby is an open-source content management system. Prior to 4.9.4 and 5.4.4, Kirby sites and plugins that use the writer or list fields or call Dom::sanitize(), Sane::sanitize(), Sane::Html::sanitize(), Sane::Svg::sanitize(), Sane::Xml::sanitize(), Sane::sanitizeFile(), or file sanitizeContents()…
When was CVE-2026-54002 disclosed?
CVE-2026-54002 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54002 actively exploited?
CVE-2026-54002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.6% of all scored CVEs.
What is the CVSS score of CVE-2026-54002?
CVE-2026-54002 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-54002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54002, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54002

Explore →

Is Your Infrastructure Affected by CVE-2026-54002?

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