Skip to main content

October CVE-2026-24906

| EUVDEUVD-2026-22659 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-04-14 GitHub_M GHSA-6qmh-j78v-ffp7
5.1
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain backend editor credentials
  2. Delivery
    Access Editor Settings panel
  3. Exploit
    Inject malicious JavaScript in Markup Classes field
  4. Install
    Save settings with XSS payload
  5. C2
    Privileged user opens RichEditor
  6. Execute
    Froala renders unsanitized dropdown
  7. Impact
    JavaScript executes in superuser context
  8. Step 8
    Attacker escalates privileges or exfiltrates session

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

CVSS 5.1 with vector AV:N/AC:L/PR:L/UI:P indicates network-accessible but requires low attack complexity, authenticated user (PR:L), and user interaction (UI:P). The scope is unchanged, and the impact is low to multiple attributes (VC:L, VI:L). While the base CVSS score is moderate, the stored XSS nature and privilege escalation scenario elevate real-world risk: an unprivileged editor can craft a payload that executes when a superuser later opens any RichEditor, potentially allowing session hijacking, CSRF attacks on behalf of the superuser, or direct privilege escalation via admin panel actions. Authentication requirement (PR:L) limits attack surface to users with backend access-a common but non-trivial barrier in many deployments. User interaction is required, but opening an editor during routine content work is expected behavior, making the UI:P less of a mitigating factor. The attack is highly automatable once a payload is crafted. Per SSVC logic, the technical impact is complete (privilege escalation), and exploitation is probable given the straightforward nature of XSS injection. This is a priority for environments where backend users span multiple trust levels (editors, contributors, admins).

Exploit ScenarioDerived

An attacker with authenticated backend access and permission to modify editor settings (e.g., a rogue contributor or compromised editor account) injects a malicious JavaScript payload into one of the Markup Classes fields, such as: test' onload='fetch(/admin/users/1?name=attacker). When a superuser or other privileged user opens a RichEditor to edit a blog post or page, the Froala editor renders the unsanitized Markup Classes dropdown, executing the embedded JavaScript in the superuser's browser session. The attacker can then perform actions on behalf of the superuser, such as creating a new admin account or modifying security settings. The stored nature of the XSS means the payload persists and re-executes for every user who opens an editor, making it a highly effective privilege escalation vector.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 14, 2026

Stored Cross-Site Scripting (XSS) in October CMS versions prior to 3.7.14 and 4.1.10 allows authenticated backend users with editor settings permissions to inject malicious JavaScript into Markup Classes fields, which executes unsanitized in the Froala editor dropdown menus when any user-including superusers-opens a RichEditor. This enables privilege escalation when a superuser performs routine content editing tasks. CVSS 5.1 indicates moderate risk; exploitation requires authenticated backend access and user interaction (opening an editor), but the stored nature of the payload and privilege escalation potential elevate real-world concern. No public exploit code or active CISA KEV status reported.

RemediationAI

Upgrade October CMS to version 3.7.14 or 4.1.10 or later, which include input sanitization for Markup Classes fields. Vendor-released patches are available at https://github.com/octobercms/october/security/advisories/GHSA-6qmh-j78v-ffp7. As an interim workaround, restrict editor settings permissions to fully trusted administrators only, thereby preventing unprivileged users from injecting payloads into Markup Classes fields. Monitor backend access logs for suspicious editor settings modifications and review existing Markup Classes values for any suspicious or malformed entries that may indicate prior exploitation attempts.

Affected VersionsENISA

October < 3.7.14
October 4.0.0, < 4.1.10

Affected Packages

composer october/system fix: 3.7.14, 4.1.10
euvd october fix: 3.7.14, 4.1.10

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in composer, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

October CMS is a Laravel-based content management system (CPE: cpe:2.3:a:octobercms:october:*:*:*:*:*:*:*:*). The vulnerability stems from CWE-79 (Improper Neutralization of Input During Web Page Generation), specifically in the backend Editor Settings component. The Markup Classes fields-used to define paragraph styles, inline styles, and table styles-accept user input that is rendered directly into the Froala rich-text editor's dropdown menus without sanitization. The Froala editor, a third-party JavaScript component, renders these class definitions in the DOM; because the input was not restricted to valid CSS class name characters (which should match the regex [a-zA-Z_-][a-zA-Z0-9_-]*), an attacker can inject HTML/JavaScript payloads. When these unsanitized values are rendered into the editor's UI, the browser executes any embedded scripts in the context of the authenticated user's session.

Know when October gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 5.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
Passive
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Patch released
Apr 15, 2026 - 02:30 nvd
Patch available
CVSS changed
Apr 14, 2026 - 18:22 NVD
5.1 (MEDIUM)
CVE Published
Apr 14, 2026 - 17:23 nvd
MEDIUM 5.1

DescriptionCVE.org

October is a Content Management System (CMS) and web platform. Versions prior to 3.7.14 and 4.1.10 contain a Stored Cross-Site Scripting (XSS) vulnerability in the Backend Editor Settings. The Markup Classes fields (used for paragraph styles, inline styles, table styles, etc.) did not sanitize input to valid CSS class name characters. Malicious values were rendered unsanitized in Froala editor dropdown menus, allowing JavaScript execution when any user opened a RichEditor. Exploitation could lead to privilege escalation if a superuser opens any RichEditor during routine content editing (e.g., editing a blog post), and requires authenticated backend access with editor settings permissions. This issue has been fixed in versions 3.7.14 and 4.1.10. To workaround this issue, restrict editor settings permissions to fully trusted administrators only

Threat Intelligence Overview

EPSS Score
0.1%
Top 80% exploitable
Threat Intel
1
1 source
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2017-1000119 HIGH POC
7.2 Oct 05

October CMS build 412 is vulnerable to PHP code execution in the file upload functionality resulting in site compromise

CVE-2021-3311 CRITICAL POC
9.8 Feb 05

An issue was discovered in October through build 471. Rated critical severity (CVSS 9.8), this vulnerability is remotely

CVE-2021-32648 CRITICAL POC
9.1 Aug 26

octobercms in a CMS platform based on the Laravel PHP Framework. Rated critical severity (CVSS 9.1), this vulnerability

CVE-2017-16244 HIGH POC
8.8 Nov 01

Cross-Site Request Forgery exists in OctoberCMS 1.0.426 (aka Build 426) due to improper validation of CSRF tokens for po

CVE-2022-21705 HIGH POC
7.2 Feb 23

Octobercms is a self-hosted CMS platform based on the Laravel PHP Framework. Rated high severity (CVSS 7.2), this vulner

CVE-2018-7198 MEDIUM POC
6.1 Feb 18

October CMS through 1.0.431 allows XSS by entering HTML on the Add Posts page. Rated medium severity (CVSS 6.1), this vu

CVE-2017-1000196 CRITICAL
9.8 Nov 17

October CMS build 412 is vulnerable to PHP code execution in the asset manager functionality resulting in site compromis

CVE-2017-1000197 CRITICAL
9.8 Nov 17

October CMS build 412 is vulnerable to file path modification in asset move functionality resulting in creating creating

CVE-2017-1000194 CRITICAL
9.8 Nov 17

October CMS build 412 is vulnerable to Apache configuration modification via file upload functionality resulting in site

CVE-2017-15284 MEDIUM POC
5.4 Oct 12

Cross-Site Scripting exists in OctoberCMS 1.0.425 (aka Build 425), allowing a least privileged user to upload an SVG fil

CVE-2015-5613 MEDIUM POC
5.4 Sep 28

Cross-site scripting (XSS) vulnerability in October CMS build 271 and earlier allows remote attackers to inject arbitrar

CVE-2023-43876 MEDIUM POC
5.4 Sep 28

A Cross-Site Scripting (XSS) vulnerability in installation of October v.3.4.16 allows an attacker to execute arbitrary w

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy