Stored XSS via unsanitized editor class names
Published Apr 14, 2026 · Updated Apr 14, 2026
Stored XSS in October CMS before 3.7.14 and 4.0.0 through 4.1.9 allows remote authenticated users to execute JavaScript in editors. Backend Editor Markup Classes accept characters outside valid CSS class names and render malicious values without sanitization in Froala RichEditor dropdowns. Editor-settings permission is required to plant a value, and a user must open any RichEditor; opening it as a superuser exposes that account to privilege escalation.
Summary
What happened
Stored XSS in October CMS before 3.7.14 and 4.0.0 through 4.1.9 allows remote authenticated users to execute JavaScript in editors. Backend Editor Markup Classes accept characters outside valid CSS class names and render malicious values without sanitization in Froala RichEditor dropdowns. Editor-settings permission is required to plant a value, and a user must open any RichEditor; opening it as a superuser exposes that account to privilege escalation.
The record
- CVE
- CVE-2026-24906
- Published
- Apr 14, 2026
- Updated
- Apr 14, 2026
- Vendor
- October CMS
- Product
- October CMS
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 14, 2026CVE publishedPublication date reported by the CVE source.
- Apr 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.7.14
- Affected versionversion=>= 4.0.0, < 4.1.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo