Skip to main content
VulnerabilityPublished

CVE-2026-91115: silverstripe-framework · Reflection Injection

Affects silverstripe-frameworkSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 6.2.13 soon.

Data as of 16 Nov 2026, 16:50 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.8
Patch
Available – fixed in 6.2.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 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 15 Nov 2026.

What to do

Upgrade silverstripe-framework to 6.2.13.

Affected software

ProductAffectedFixed in
silverstripesilverstripe-frameworkAffected
  • >=6.0.0 <6.2.13
Fixed in
  • 6.2.13

AI-suggested

Upgrade Silverstripe Framework to version 6.2.13 or later, where this vulnerability is fixed. Until the upgrade, avoid exposing development mode interfaces publicly and do not follow untrusted development task URLs. No other vendor mitigation or temporary fixes are indicated.

Description

CVE-2026-91115 is a high-severity vulnerability in the Silverstripe Framework versions 6.0.0 through 6.2.12. It involves reflection injection via the writer option of the i18nTextCollectorTask, allowing an attacker to instantiate arbitrary objects with controlled constructor arguments and execute code on the server. This can be triggered by an administrator following a crafted dev task URL, as the nested task requires no confirmation and is exposed in development mode without authentication. The issue is fixed in version 6.2.13.

References

Community reviews

Loading reviews…