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

> Remote attackers can execute arbitrary code via crafted payloads in the Markup Sandbox feature of the inducer relate library.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-vpgr-vqw9-62cw

## What is CVE-2024-32404?

CVE-2024-32404 is a medium-severity code injection vulnerability in n/a, published on 26 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Server-Side Template Injection (SSTI) vulnerability in inducer relate before v.2024.1, allows remote attackers to execute arbitrary code via a crafted payload to the Markup Sandbox feature.

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

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

It affects 1 product.


Products: Inducer Relate.

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

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

## Is CVE-2024-32404 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-41588](https://insights.sbomify.com/CVE-2026-41588/): RELATE: Timing Attack Vulnerability in course/auth.py — check_sign_in_key() (critical 9.0)
- [CVE-2024-32407](https://insights.sbomify.com/CVE-2024-32407/): Server-side request forgery in n/a (high 8.8)
- [CVE-2024-32406](https://insights.sbomify.com/CVE-2024-32406/): Code injection in n/a (high 7.5)
- [CVE-2024-32405](https://insights.sbomify.com/CVE-2024-32405/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32404 is a medium-severity code injection vulnerability in n/a, published on 26 Apr 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-32404 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-32404/ (Markdown: https://insights.sbomify.com/CVE-2024-32404/index.md)
```

## Sources

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

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