Answer in brief
CVE-2026-91114 records a Medium severity (CVSS 4.4) vulnerability in Silverstripe Framework: Stored XSS via unescaped permission in PermissionCheckboxSetField. The current sources do not mark it as known exploited. The current feed maps silverstripe/silverstripe-framework (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps silverstripe/silverstripe-framework (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| silverstripe/silverstripe-frameworkgeneric | <6.2.13 | 6.2.13 |
Published upstream
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 16, 2026
Silverstripe Framework is a PHP framework which powers the Silverstripe CMS. Prior to 6.2.13, PermissionCheckboxSetField accepts permission codes that the field did not offer and stores them without an allowlist, then renders permission codes without escaping them. A user with access to the Security section can save attacker-controlled content as a permission code, causing JavaScript to execute in the browser of another user who views the field. This issue is fixed in version 6.2.13.
Quoted source text, attributed separately from HOL analysis.