Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Editor credentials
-
DeliveryInject ${ENV_VAR} into page settings field
-
ExploitServer parses settings via parse_ini_string()
-
ExecutionEnvironment variable resolved and stored
-
ImpactAttacker reopens page and retrieves exposed secret
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | While the CVSS score of 4.9 appears moderate, the actual real-world risk is elevated by several factors. The vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N indicates network-accessible exploitation with low attack complexity and no user interaction required, but requires high privileges (Editor role). The confidentiality impact is rated High, reflecting direct exposure of secrets like database passwords and API keys. EPSS score is not provided, but the publicly documented nature and straightforward exploitation method (simple text injection) suggest automatable exploitation probability is high. The vulnerability does not appear in CISA KEV status at analysis time, and no public proof-of-concept exploit code is independently confirmed in the provided data, though the attack is trivial to replicate once Editor access is obtained. Real-world risk depends heavily on organizational controls: sites that restrict Editor access to fully trusted administrators significantly reduce impact, while sites that grant Editor access broadly to content teams face substantial risk of credential exfiltration. The fact that cms.safe_mode must be enabled limits blast radius compared to a pre-authentication vulnerability, but many productions enable this mode precisely because they want to allow safe content editing without PHP execution, making this a relevant threat vector. |
| Exploit ScenarioDerived | A compromised or malicious Editor-level account (such as a disgruntled content contributor with edit permissions) opens a page in the CMS, navigates to settings fields, and injects the text ${DB_PASSWORD} into a field like page description or metadata. Upon saving, the CMS parses this field through parse_ini_string(), which resolves ${DB_PASSWORD} to the actual database password from the server's environment variables. When the attacker reopens the same page or views the rendered output, the resolved password is displayed, allowing credential theft. If the environment also exports AWS_ACCESS_KEY_ID or APP_KEY, those are similarly exfiltrated. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 14, 2026
October CMS versions prior to 3.7.14 and 4.1.10 allow authenticated editors to disclose sensitive environment variables through PHP's parse_ini_string() interpolation syntax in page settings fields. An attacker with Editor access can inject patterns like ${APP_KEY} or ${DB_PASSWORD} into CMS configuration fields, causing the server to resolve and expose database passwords, AWS credentials, and application keys, potentially enabling database compromise or session forgery. The vulnerability is limited to installations with cms.safe_mode enabled; CVSS 4.9 reflects high confidentiality impact but requires elevated privileges (PR:H) to exploit.
RemediationAI
Vendor-released patch: October 3.7.14 or October 4.1.10 and later. Organizations should upgrade to these versions immediately. For teams unable to upgrade immediately, implement access controls restricting Editor tool permissions to a minimal set of fully trusted administrators only, verify that database credentials, API keys, and cloud service credentials are not accessible from environment variables that the web server process can read, and consider temporarily disabling cms.safe_mode if Editor access cannot be restricted (though this changes the security model). Apply the patch as soon as feasible per the GitHub security advisory at https://github.com/octobercms/october/security/advisories/GHSA-g6v3-wv4j-x9hg.
Affected VersionsENISA
Affected Packages
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 uses PHP's parse_ini_string() function to parse INI-formatted settings stored in page configuration fields. The parse_ini_string() function, when parsing INI syntax, automatically interpolates environment variables referenced using ${VARIABLE_NAME} notation. This is a documented PHP feature intended for variable substitution, but becomes a security issue when untrusted user input (from authenticated editors) is passed directly to this parser without sanitization. The vulnerability is rooted in CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and occurs because user-controlled settings data is processed by a function that resolves sensitive system variables. The cms.safe_mode setting is relevant because when disabled, October already prevents arbitrary PHP injection; when enabled, it restricts code execution but does not prevent INI variable interpolation, creating this specific disclosure path.
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
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
October is a Content Management System (CMS) and web platform. Versions prior to 3.7.14 and 4.1.10 contain a server-side information disclosure vulnerability in the INI settings parser. Because PHP's parse_ini_string() function supports ${} syntax for environment variable interpolation, attackers with Editor access could inject patterns such as ${APP_KEY} or ${DB_PASSWORD} into CMS page settings fields, causing sensitive environment variables to be resolved, stored in the template, and returned to the attacker when the page was reopened. This could enable exfiltration of credentials and secrets (database passwords, AWS keys, application keys), potentially leading to further attacks such as database access or cookie forgery. The vulnerability is only relevant when cms.safe_mode is enabled, as direct PHP injection is already possible otherwise. This issue has been fixed in versions 3.7.14 and 4.1.10. If users are unable to immediately upgrade, they can workaround this issue by restricting Editor tool access to fully trusted administrators only, and ensuring database and cloud service credentials are not accessible from the web server's network.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
October CMS build 412 is vulnerable to PHP code execution in the file upload functionality resulting in site compromise
An issue was discovered in October through build 471. Rated critical severity (CVSS 9.8), this vulnerability is remotely
octobercms in a CMS platform based on the Laravel PHP Framework. Rated critical severity (CVSS 9.1), this vulnerability
Cross-Site Request Forgery exists in OctoberCMS 1.0.426 (aka Build 426) due to improper validation of CSRF tokens for po
Octobercms is a self-hosted CMS platform based on the Laravel PHP Framework. Rated high severity (CVSS 7.2), this vulner
October CMS through 1.0.431 allows XSS by entering HTML on the Add Posts page. Rated medium severity (CVSS 6.1), this vu
October CMS build 412 is vulnerable to PHP code execution in the asset manager functionality resulting in site compromis
October CMS build 412 is vulnerable to file path modification in asset move functionality resulting in creating creating
October CMS build 412 is vulnerable to Apache configuration modification via file upload functionality resulting in site
Cross-Site Scripting exists in OctoberCMS 1.0.425 (aka Build 425), allowing a least privileged user to upload an SVG fil
Cross-site scripting (XSS) vulnerability in October CMS build 271 and earlier allows remote attackers to inject arbitrar
A Cross-Site Scripting (XSS) vulnerability in installation of October v.3.4.16 allows an attacker to execute arbitrary w
EUVD-2026-22704
GHSA-g6v3-wv4j-x9hg
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB