Host command execution via evaluated engine name
Published Jan 19, 2026 · Updated Jan 19, 2026
Eval injection in Alchemy CMS before 7.4.12 and 8.0.0 through 8.0.2 allows local users to execute arbitrary host commands. Alchemy::ResourcesHelper#resource_url_proxy passes resource_handler.engine_name to Ruby eval(), interpreting module configuration as code. Exploitation requires local file access to alter the module configuration and runs commands with the CMS host process privileges.
Summary
What happened
Eval injection in Alchemy CMS before 7.4.12 and 8.0.0 through 8.0.2 allows local users to execute arbitrary host commands. Alchemy::ResourcesHelper#resource_url_proxy passes resource_handler.engine_name to Ruby eval(), interpreting module configuration as code. Exploitation requires local file access to alter the module configuration and runs commands with the CMS host process privileges.
The record
- CVE
- CVE-2026-23885
- Published
- Jan 19, 2026
- Updated
- Jan 19, 2026
- Vendor
- AlchemyCMS
- Product
- Alchemy CMS
- Classifications
- CWE-95, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 19, 2026CVE publishedPublication date reported by the CVE source.
- Jan 19, 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=< 7.4.12
- Affected versionversion=>= 8.0.0, < 8.0.3
What conditions does exploitation require?
What is affected?
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
- Vendor advisory standalone Ruby proof of conceptproof of concept · demonstrated
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