CVE-2026-91110

MEDIUMPre-NVD 6.46.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th 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

Also known asEUVD-2026-126498 (ENISA EUVD)Source: ENISA EUVD

6.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not normalize certain control bytes that browsers ignore when parsing URLs. A CMS author can place those bytes before a javascript: URL in stored content so the sanitiser misses the dangerous scheme, and JavaScript executes in the browser of another user who views the content. This issue is fixed in version 6.2.13.

CVSS v3
6.4
EG Score
6.4MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity64% × 45%
Impact severity (EG Severity): CVSS 6.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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
8th
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 (6.4): severity, escalated by confirmed exploitation. This CVE's 6.4 is its impact severity (EG Severity), not escalated.

EG Severity
6.4 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-11-17). 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 every mission impact level.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 every mission impact level.

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

Exploitation none (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

November 16, 2026

Last Modified

November 17, 2026

Advisory Details (5)

Auto-updated Nov 16, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)

XSS using control bytes · Advisory · silverstripe/silverstripe-framework · GitHub

https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-m5w3-5gq7-2crg
GitHub release Patch Available

6.2.13

Patch available: silverstripe/silverstripe-framework 6.2.13

https://github.com/silverstripe/silverstripe-framework/releases/tag/6.2.13
GitHub pull request Patch Available

[CVE-2026-91110] XSS using control bytes

Patch available: silverstripe/silverstripe-framework 6.2.13 (PR #12038 merged 2026-10-28)

https://github.com/silverstripe/silverstripe-framework/pull/12038
GitHub commit Patch Available

commit dbf965166da9 (silverstripe/silverstripe-framework)

Patch available: silverstripe/silverstripe-framework 6.2.13 (contains commit dbf965166da9)

https://github.com/silverstripe/silverstripe-framework/commit/dbf965166da909739a197c95b27dd9ee2fde93c9

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-11-17 17:30 UTCEchelonGraph re-scored
  6. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-11-17 16:29 UTCEchelonGraph re-scored
  8. 2026-11-16 18:02 UTCENISA EUVD ID recordedEUVD-2026-126498 · Source: ENISA EUVD
  9. 2026-11-16 17:29 UTCEchelonGraph re-scored
  10. 2026-11-16 16:35 UTCEchelonGraph re-scoredFirst assessed: 6.4 MEDIUM
  11. 2026-11-16 16:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91110?
CVE-2026-91110 is a medium-severity vulnerability; its CVE record was published on November 16, 2026. Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, the HTML sanitiser does not normalize certain control bytes that browsers ignore when parsing URLs. A CMS author can place those bytes before a javascript: URL in stored content so the sanitiser misses the…
When was the CVE record for CVE-2026-91110 published?
The CVE record for CVE-2026-91110 was published on November 16, 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 November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-91110 actively exploited?
CVE-2026-91110 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91110?
CVE-2026-91110 has a CVSS base score of 6.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-91110?
A fix for CVE-2026-91110 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-91110?

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