CVE-2024-22533 — beetl-core
CRITICALCVE-2024-22533 is a critical-severity (CVSS 9.8) Code Injection vulnerability in com.ibeetl:beetl-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.ibeetl:beetl-core — see the affected versions and patch details below.
Beetl Server-Side Template Injection vulnerability
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-22533.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.ibeetl:beetl-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Before Beetl v3.15.13.RELEASE, the rendering template has a server-side template injection (SSTI) vulnerability. When the incoming template is controllable, it will be filtered by the DefaultNativeSecurityManager blacklist. Because blacklist filtering is not strict, the blacklist can be bypassed, leading to arbitrary code execution.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.ibeetl:beetl-core | all versions | 3.15.13.RELEASEcom.ibeetl:beetl-core:3.15.13.RELEASE |
Affected Products
beetlxiandafuResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.ibeetl:beetl-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.ibeetl:beetl-core to 3.15.13.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22533 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2024-22533 in your dependencies?
Find it across Maven, including transitive dependencies.