CVE-2026-91115
Silverstripe Framework vulnerability
- Published16 Nov 2026
Description
Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. From 6.0.0 until 6.2.13, the writer option of i18nTextCollectorTask is passed to the dependency injector without validating that it names an allowed writer implementation. A crafted dev task URL can therefore instantiate arbitrary objects with attacker-controlled constructor arguments and execute code on the server. An administrator can be induced to run the task by following a link because the nested task did not require confirmation, and a site in dev mode exposes the path without authentication. CMS 5 is not affected. This issue is fixed in version 6.2.13.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://github.com/silverstripe/silverstripe-framework/commit/2df498b1fad25db95dbd882117dcd0527a5fdbfa
- https://github.com/silverstripe/silverstripe-framework/pull/12035
- https://github.com/silverstripe/silverstripe-framework/releases/tag/6.2.13
- https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-c94f-87xg-65wf
- https://www.silverstripe.org/download/security-releases/cve-2026-91115
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-91115 being actively exploited?
CVE-2026-91115 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.64%.
How severe is CVE-2026-91115?
CVE-2026-91115 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.64% probability of exploitation.
How do I fix CVE-2026-91115?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-91115 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. The CVSS 4.0 base score is shown where the NVD has one, otherwise CVSS 3.1.