CVE-2026-25125: October CMS: Environment Variable Exfiltration via INI Parser Interpolation
A server-side information disclosure vulnerability was identified in the INI settings parser. PHP's parseinistring() function supports ${} syntax for environment variable interpolation. Attackers with Editor access could inject ${APPKEY}, ${DBPASSWORD}, or similar patterns into CMS page settings fields, causing sensitive environment variables to be resolved and stored in the template. These values were then returned to the attacker when the page was reopened.
Impact - Exfiltration of sensitive environment variables (APPKEY, DB credentials, AWS keys, etc.) - Could enable further attacks: database access, cookie forgery, AWS resource access - Requires authenticated backend access with Editor permissions - Only relevant when cms.safemode is enabled (otherwise direct PHP injection is already possible)
Patches The vulnerability has been patched in v3.7.14 and v4.1.10. All users are encouraged to upgrade to the latest patched version.
Workarounds If upgrading immediately is not possible: - Restrict Editor tool access to fully trusted administrators only - Ensure database and cloud service credentials are not accessible from the web server's network
References - Reported by Proactive Testing Team (PTT)
Other sources
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 parseinistring() function supports ${} syntax for environment variable interpolation, attackers with Editor access could inject patterns such as ${APPKEY} or ${DBPASSWORD} 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.safemode 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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/october/rainto a version that resolves this vulnerability.Fixed in 3.7.14 - Upgrade
Upgrade
composer/october/rainto a version that resolves this vulnerability.Fixed in 4.1.10 - Upgrade
Upgrade
October CMSto a version that resolves this vulnerability.Fixed in 3.7.14 - Upgrade
Upgrade
October CMSto a version that resolves this vulnerability.Fixed in 4.1.10 - Compensating control
Restrict Editor tool access to fully trusted administrators only (issue requires authenticated backend access with Editor permissions).
- Compensating control
Ensure database and cloud service credentials are not accessible from the web server's network (limit reachability so exfiltrated ${DB_PASSWORD}/AWS keys cannot be used for database access or AWS resource access).
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25125?
CVE-2026-25125 is classified as a medium-severity vulnerability due to its potential for information disclosure.
How do I fix CVE-2026-25125?
To fix CVE-2026-25125, upgrade October CMS to versions 3.7.14 or 4.1.10 or later.
What is the impact of CVE-2026-25125?
CVE-2026-25125 allows attackers to exfiltrate sensitive environment variables through the INI parser, leading to potential server-side information disclosure.
Which versions of October CMS are vulnerable to CVE-2026-25125?
Versions of October CMS prior to 3.7.14 and 4.1.10 are vulnerable to CVE-2026-25125.
Is CVE-2026-25125 an active exploit?
As of now, there are no known active exploits for CVE-2026-25125, but it is advisable to apply the necessary updates promptly.