# CVE-2024-55652: PwnDoc Server-Side Template Injection vulnerability - Sandbox Escape to RCE using custom filters

> An attacker with admin privileges can execute arbitrary code on the server by uploading a malicious document template that escapes the JavaScript sandbox.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2024
- **Updated:** 12 Dec 2024
- **Also known as:** GHSA-jw5r-6927-hwpc

## What is CVE-2024-55652?

CVE-2024-55652 is a medium-severity code injection vulnerability in pwndoc, published on 11 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

PenDoc is a penetration testing reporting application. Prior to commit 1d4219c596f4f518798492e48386a20c6e9a2fe6, an attacker can write a malicious docx template containing expressions that escape the JavaScript sandbox to execute arbitrary code on the system. An attacker who can control the contents of the template document is able to execute arbitrary code on the system. By default, only users with the `admin` role are able to create or update templates. Commit 1d4219c596f4f518798492e48386a20c6e9a2fe6 patches the issue.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2024-55652?


## How do I fix CVE-2024-55652?

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

## Is CVE-2024-55652 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-55652 and fix it if it is affected.

What it is: CVE-2024-55652 is a medium-severity code injection vulnerability in pwndoc, published on 11 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-55652 exists.

Affected product: pwndoc. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-55652/ (Markdown: https://insights.sbomify.com/CVE-2024-55652/index.md)
```

## Sources

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

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