Loading vulnerability…
CVE-2026-66748 is an authenticated remote code execution vulnerability in Camaleon CMS versions 2.1.1 through 2.9.1. The flaw is in handling of the select_eval custom field type, where a user with custom_fields manage permission can supply a malicious Ruby expression and store it in the custom field options command parameter. That attacker-controlled expression is later evaluated via instance_eval within an ERB view when a post edit page is rendered. Because untrusted input is executed as Ruby code on the server, successful exploitation results in arbitrary server-side code execution in the context of the web server process.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small standalone exploit PoC for CVE-2026-66748 affecting Camaleon CMS 2.1.1 through 2.9.1. It contains one Python exploit script and one README advisory. The Python script uses requests.Session to authenticate to the CMS admin interface, scrape CSRF tokens from /admin/login and /admin/dashboard, create a malicious custom field group via /admin/settings/custom_fields, and then trigger execution by loading /admin/post_type/{TYPE_ID}/posts/{POST_ID}/edit. The exploit abuses the select_eval custom field type, which stores attacker-controlled Ruby in field_options[*][command]; that Ruby is later executed with instance_eval when the edit form renders. The included default payload is a Ruby one-liner that launches a bash reverse shell to ATTACKER_IP:4444 in a background thread. Commented alternatives include a pure Ruby socket backdoor and a benign proof-of-concept that displays id/hostname in the dropdown. Overall, this is a valid authenticated web RCE exploit, not merely a detector. It requires low privileges but valid credentials with custom_fields management rights, and provides arbitrary Ruby execution in the Rails process with persistence because the malicious field executes whenever affected edit pages are rendered.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.