# CVE-2023-30331: Server-side template injection in beetl

> Attackers can execute arbitrary code via server-side template injection in the Beetl Java template engine library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2023
- **Updated:** 29 Jan 2025
- **Also known as:** GHSA-m69h-4frq-vwq7

## What is CVE-2023-30331?

CVE-2023-30331 is a critical code injection vulnerability in n/a, published on 4 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the render function of beetl v3.15.0 allows attackers to execute server-side template injection (SSTI) via a crafted payload.

## Which versions are affected by CVE-2023-30331?

2 open source packages ship an affected version, including com.ibeetl:beetl. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.ibeetl:beetl` | Maven | All versions to 3.15.0.RELEASE | None |
| `com.ibeetl:beetl` | Maven | All versions to 3.15.0.RELEASE | None |

Products: Beetl Project Beetl.

## How do I fix CVE-2023-30331?

No fix has been published for CVE-2023-30331 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-30331 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30331 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30331 and fix it if it is affected.

What it is: CVE-2023-30331 is a critical code injection vulnerability in n/a, published on 4 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30331 exists.

Affected packages and fixed versions:
- com.ibeetl:beetl (Maven): affected all versions up to 3.15.0.RELEASE; no fix listed
- com.ibeetl:beetl (Maven): affected all versions up to 3.15.0.RELEASE; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-30331/ (Markdown: https://insights.sbomify.com/CVE-2023-30331/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-30331
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-30331
- OSV: https://osv.dev/vulnerability/CVE-2023-30331

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-30331/
Summaries are generated and may contain mistakes; the official description above is the record.