Loading vulnerability…
CVE-2025-6384 is an improper control of dynamically managed code resources vulnerability in Crafter Studio, a component of CrafterCMS. An authenticated developer can insert malicious Groovy elements that bypass the intended Groovy sandbox restrictions, resulting in execution of operating system commands. The issue affects CrafterCMS versions 4.0.0 through 4.2.2.
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 (1 hidden).
This repository documents a proof-of-concept (PoC) exploit for CVE-2025-6384, an authenticated remote code execution (RCE) vulnerability in CrafterCMS's Crafter Studio component. The vulnerability allows an authenticated user with developer privileges to bypass the Groovy script sandbox and execute arbitrary system commands or spawn a reverse shell. The exploit is achieved by uploading a malicious Groovy script via the Crafter Studio web interface, which instantiates a new GroovyShell object, thus escaping the intended sandbox restrictions. The README provides detailed steps for setting up a vulnerable environment, crafting and deploying the exploit payload, and verifying successful exploitation. No actual exploit code files are present in the repository; all payloads are provided as code snippets within the README. The main endpoints involved are the Crafter Studio web interface and the file paths where the malicious scripts are uploaded. The exploit is classified as a proof-of-concept (POC) and is not weaponized.
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.
6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.