Loading vulnerability…
An arbitrary file write vulnerability exists in Camaleon CMS prior to version 2.8.2, specifically in the upload method of the MediaController. Authenticated users can write files to any location on the server, subject to filesystem permissions. This can be exploited to achieve delayed remote code execution, for example by writing a Ruby file into the config/initializers/ directory of the Rails application.
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 provides a Python exploit script (exploit_camaleon.py) targeting CVE-2024-46986, an arbitrary file upload vulnerability in Camaleon CMS. The exploit requires valid user credentials (auth_token and _cms_session) and the target URL. It automates the upload of a malicious Ruby script to the server via a vulnerable file upload endpoint (/admin/media/upload?actions=false). The attacker can choose between two payloads: a reverse shell (which connects back to the attacker's machine) or a command execution payload (allowing repeated arbitrary command execution on the server). The script constructs a multipart/form-data POST request to upload the payload into the server's config/initializers directory. The exploit is operational and provides remote code execution capabilities. The repository consists of a detailed README and a single Python exploit script.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.