Alchemy Cms
Approved changes feed: RSS · Atom
cpe:2.3:a:alchemycms:alchemy_cms:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Alchemycms (8da886a0-6ed5-5b6a-b36e-bfe826b07346) |
|---|---|
| Product | Alchemy Cms (2c6bc344-4605-5bfc-b8f3-2e62bfee6118) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-23885 |
vulnerable | 2026-06-08 07:51:16.386877 |
AlchemyCMS has Authenticated Remote Code Execution (RCE) via eval injection in ResourcesHelper
MEDIUM (6.4)
Alchemy is an open source content management system engine written in Ruby on Rails. Prior to versions 7.4.12 and 8.0.3, the application uses the Ruby `eval()` function to dynamically execute a string provided by the `resource_handler.engine_name` attribute in `Alchemy::ResourcesHelper#resource_url_proxy`. The vulnerability exists in `app/helpers/alchemy/resources_helper.rb` at line 28. The code explicitly bypasses security linting with `# rubocop:disable Security/Eval`, indicating that the use of a dangerous function was known but not properly mitigated. Since `engine_name` is sourced from module definitions that can be influenced by administrative configurations, it allows an authenticated attacker to escape the Ruby sandbox and execute arbitrary system commands on the host OS. Versions 7.4.12 and 8.0.3 fix the issue by replacing `eval()` with `send()`.
Published: 2026-01-19T21:09:06.757Z
Updated: 2026-01-21T21:12:51.110Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.