{"answers":{"affected":"2 open source packages ship an affected version, including org.craftercms:crafter-studio. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-6384 in the wild and no public exploit code.","fix":"Upgrade org.craftercms:crafter-studio to 4.3.0 or later.","what":"CVE-2025-6384 is a high-severity code injection vulnerability in CrafterCMS, published on 19 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6384 and fix it if it is affected.\n\nWhat it is: CVE-2025-6384 is a high-severity code injection vulnerability in CrafterCMS, published on 19 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-6384 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.craftercms:crafter-studio (Maven): affected from 4.0.0; fixed in 4.3.0\n- org.craftercms:crafter-studio (Maven): affected from 4.0.0; fixed in 4.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-6384/ (Markdown: https://insights.sbomify.com/CVE-2025-6384/index.md)","id":"CVE-2025-6384","markdown":"https://insights.sbomify.com/CVE-2025-6384/index.md","name":"CVE-2025-6384","record":{"aliases":["GHSA-5644-3vgq-2ph5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"CrafterCMS Studio","requires_auth":"high_privilege","summary":"Authenticated developers can bypass Groovy Sandbox restrictions to execute arbitrary OS commands, leading to remote code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"crafter","cpe":[{"product":"craftercms","vendor":"craftercms"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"}],"description":"Improper Control of Dynamically-Managed Code Resources vulnerability in Crafter Studio of CrafterCMS allows authenticated developers to execute OS commands via Groovy Sandbox Bypass.\n\nBy inserting malicious Groovy elements, an attacker may bypass Sandbox restrictions and obtain RCE (Remote Code Execution).\n\nThis issue affects CrafterCMS: from 4.0.0 through 4.2.2.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2025-08-08","github_poc":2,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-08-08T20:25:47Z","kind":"github_poc","ref":"https://github.com/mbadanoiu/CVE-2025-6384","stars":0,"title":"CVE-2025-6384: Groovy Sandbox Bypass 2 in CrafterCMS"},{"date":"2025-09-26T02:08:30Z","kind":"github_poc","ref":"https://github.com/maestro-ant/CrafterCMS-CVE-2025-6384","stars":0,"title":"PoC exploit for an authenticated RCE in CrafterCMS via Groovy sandbox bypass (CVE-2025-6384)"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Improper Control of Dynamically-Managed Code Resources in Crafter Studio","id":"CVE-2025-6384","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"WP Applink \u003c= 0.4.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via title Parameter","id":"CVE-2025-6385"},"packages":[{"ecosystem":"Maven","fixed":["4.3.0"],"introduced":["4.0.0"],"last_affected":[],"package":"org.craftercms:crafter-studio","purl":null,"source":"GHSA-5644-3vgq-2ph5"},{"ecosystem":"Maven","fixed":["4.3.0"],"introduced":["4.0.0"],"last_affected":[],"package":"org.craftercms:crafter-studio","purl":"pkg:maven/org.craftercms/crafter-studio","source":"GHSA-5644-3vgq-2ph5"}],"prev":{"headline":"WP-PhotoNav \u003c= 1.2.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via photonav Shortcode","id":"CVE-2025-6383"},"products":["CrafterCMS"],"published":"2025-06-19","related":[{"cvss_score":7.4,"headline":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Crafter Engine","id":"CVE-2023-4136","kev_date_added":null,"published":"2023-08-03"},{"cvss_score":6.9,"headline":"Transmission of Private Resources into a New Sphere in Crafter Engine","id":"CVE-2025-0502","kev_date_added":null,"published":"2025-01-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-23","vendors":["CrafterCMS"]},"summary":"Authenticated developers can bypass Groovy Sandbox restrictions to execute arbitrary OS commands, leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2025-6384/"}