Skip to main content
VulnerabilityPublished

CVE-2026-54717: silverstripe-cms · Cross-site Scripting

Affects silverstripe-cmsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 6.2.1 when convenient.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade silverstripe-cms and silverstripe/silverstripe-cms to 6.2.1.

Affected software

ProductAffectedFixed in
silverstripesilverstripe-cmsAffected
  • <6.2.1
Fixed in
  • 6.2.1
GitHubsilverstripe/silverstripe-cmspkg:github/silverstripe/silverstripe-cmsOther threatsAffected
  • <6.2.1
Fixed in
  • 6.2.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Silverstripe CMS to version 6.2.1 or later, where the vulnerability is fixed by properly escaping page titles in the breadcrumb trail. No other mitigation or temporary workaround is indicated.

Description

Silverstripe CMS versions prior to 6.2.1 have a cross-site scripting (XSS) vulnerability in the page breadcrumbs feature within the CMS page list view. This occurs because page titles are rendered into the breadcrumb trail without proper escaping. The vulnerability is fixed in version 6.2.1.

References

Community reviews

Loading reviews…