# CVE-2024-54756: Code injection in n/a

> Attackers can execute arbitrary code by tricking users into loading a crafted PK3 file with malicious ZScript in GZDoom.

- **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:** 20 Feb 2025
- **Updated:** 21 Feb 2025
- **Also known as:** GHSA-8hvg-x32p-2j7j

## What is CVE-2024-54756?

CVE-2024-54756 is a critical code injection vulnerability in n/a, published on 20 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote code execution (RCE) vulnerability in the ZScript function of ZDoom Team GZDoom v4.13.1 allows attackers to execute arbitrary code via supplying a crafted PK3 file containing a malicious ZScript source file.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2024-54756 being exploited?

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

Public exploit code:

- Proof of concept for CVE-2024-54756, a vulnerability I found in GZDoom's ZScript scripting engine. (github_poc): https://github.com/Chainmanner/GZDoom-Arbitrary-Code-Execution-via-ZScript-PoC

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54756 is a critical code injection vulnerability in n/a, published on 20 Feb 2025. 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-2024-54756 exists.

Affected product: n/a. 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-54756/ (Markdown: https://insights.sbomify.com/CVE-2024-54756/index.md)
```

## Sources

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

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