CVE-2026-56393

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (13th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-38159 (ENISA EUVD) · GHSA-4mgv-366x-qxvx (GitHub Security Advisories) · GHSA-f95g-vm94-46c3 (GitHub Security Advisories)Source: ENISA EUVD

4.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.2%CVSS: 4.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Craft CMS 4.x (>= 4.0.0-RC1, < 4.17.0-beta.1) and 5.x (>= 5.0.0-RC1, < 5.9.0-beta.1) contain multiple stored cross-site scripting vulnerabilities where settings names and field option labels are rendered without sanitization (e.g., via the checkbox.twig template, which used {{ label|raw }}). An authenticated administrator (with allowAdminChanges enabled) can inject malicious payloads into section names, volume names, user group names, global set names, generated field names, checkbox/radio option labels, and custom source labels, causing arbitrary JavaScript to execute in other users' control-panel sessions. Fixed in 4.17.0-beta.1 and 5.9.0-beta.1.

CVSS v3
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity48% × 45%
Impact severity (EG Severity): CVSS 4.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.8): severity, escalated by confirmed exploitation. This CVE's 4.8 is its impact severity (EG Severity), not escalated.

EG Severity
4.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

June 21, 2026

Last Modified

October 25, 2026

Advisory Details (4)

Auto-updated Jun 25, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Multiple Stored XSS in Settings Names and Field Options · Advisory · craftcms/cms · GitHub

https://github.com/craftcms/cms/security/advisories/GHSA-4mgv-366x-qxvx
Web page

Craft CMS - Multiple Stored Cross-Site Scripting in Settings Names and Field Options | Advisories | VulnCheck

https://www.vulncheck.com/advisories/craft-cms-multiple-stored-cross-site-scripting-in-settings-names-and-field-options
GitHub commit Patch Available

commit 943152d2246b (craftcms/cms)

Patch available: craftcms/cms 5.9.21 (contains commit 943152d2246b)

https://github.com/craftcms/cms/commit/943152d2246b36f12adf161a03b8695b773d9276
GitHub commit Patch Available

commit 67780a778c6e (craftcms/cms)

Patch available: craftcms/cms 5.9.21 (contains commit 67780a778c6e)

https://github.com/craftcms/cms/commit/67780a778c6ec04e68e64a0b1177c168306144a2

Vendor Advisories for CVE-2026-56393(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composercraftcms/cms @ 5.9.0-beta.1 (fixes >= 5.0.0-RC1, < 5.9.0-beta.1)—ghsa
composercraftcms/cms @ 4.17.0-beta.1 (fixes >= 4.0.0-RC1, < 4.17.0-beta.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
craftcms/cms4.0.0 ... 4.9.7 (229 versions)
  • 5.0.0-RC1 up to 5.9.0-beta.1: fixed in 5.9.0-beta.1
  • 4.0.0-RC1 up to 4.17.0-beta.1: fixed in 4.17.0-beta.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 100 of 208 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. None are among the latest 100 rows. The 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-56393?
CVE-2026-56393 is a medium-severity vulnerability; its CVE record was published on June 21, 2026. Craft CMS 4.x (>= 4.0.0-RC1, < 4.17.0-beta.1) and 5.x (>= 5.0.0-RC1, < 5.9.0-beta.1) contain multiple stored cross-site scripting vulnerabilities where settings names and field option labels are rendered without sanitization (e.g., via the checkbox.twig template, which used {{ label|raw }}). An…
When was CVE-2026-56393 made public?
CVE-2026-56393 was made public on March 2, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 21, 2026. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56393 actively exploited?
CVE-2026-56393 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56393?
CVE-2026-56393 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56393?
A fix for CVE-2026-56393 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56393 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56393?

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