CVE-2026-45368

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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
Trending — 3 sources updated this week
8.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.4Exploit: NoneExposed: 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. In versions prior to 4.9.1 and 5.4.1, the underlying URL methods for the KirbyTags and image blocks components did not filter out malicious URL values that resolve to script execution. The vulnerability affects four first-party Kirby renderers that produce ` output from editor-supplied field values: the (link: …) KirbyTag, the link: parameter of the (image: …) KirbyTag when it does not resolve to a known file or self, the link field of the built-in image block, and the HTML importer for the blocks field (which accepted the same malicious input as the image block link field). While simple avascript: URLs were already deactivated by treating them as a relative path and prepending a single slash to the URL, the use of URLs of the format javascript://x%0A… bypasses this protection. The vbscript:, data:, livescript:, mocha: and jar:` schemes are affected by the same underlying gap. This issue has been fixed in versions 4.9.1 and 5.4.1.

CVSS v3
8.4
EG Score
8.4(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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
25.7%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 18, 2026

Advisory Details (1)

Auto-updated Jul 16, 2026
Patch available. Sources: github.
github Patch Available

Cross-site scripting (XSS) from links in KirbyTags, image blocks and imported blocks HTML in the site frontend · Advisory · getkirby/kirby · GitHub

https://github.com/getkirby/kirby/security/advisories/GHSA-qvjf-922g-pj44

Vendor Advisories for CVE-2026-45368(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.0 (22 versions)5.4.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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-07-23 03:16 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 22:05 UTCEG score recompute▲ 8.40
  8. 2026-07-16 22:05 UTCMITRE cvelistV5CVSS v3 → 8.4 · CVSS v4 → 8.4
  9. 2026-06-14 23:18 UTCEPSS rescore
  10. 2026-06-13 23:00 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-05-27 18:35 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45368?
CVE-2026-45368 is a high vulnerability published on May 27, 2026. Kirby is an open-source content management system. In versions prior to 4.9.1 and 5.4.1, the underlying URL methods for the KirbyTags and image blocks components did not filter out malicious URL values that resolve to script execution. The vulnerability affects four first-party Kirby renderers that…
When was CVE-2026-45368 disclosed?
CVE-2026-45368 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on July 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45368 actively exploited?
CVE-2026-45368 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45368?
CVE-2026-45368 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-45368?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45368, 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-45368

Explore →

Is Your Infrastructure Affected by CVE-2026-45368?

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

Start Free Scan →Browse All CVEs