# CVE-2023-25344: Code injection in n/a

> Attackers can execute arbitrary code in SWIG templates by exploiting a vulnerability in Object.prototype anonymous functions.

- **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:** 15 Mar 2023
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-rjhx-p7x7-qfq6

## What is CVE-2023-25344?

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

### Official description

An issue was discovered in swig-templates thru 2.0.4 and swig thru 1.4.2, allows attackers to execute arbitrary code via crafted Object.prototype anonymous function.

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

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

It affects 2 products.


Products: Swig-Templates Project Swig-Templates, Swig Project Swig.

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

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

## Is CVE-2023-25344 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-25345](https://insights.sbomify.com/CVE-2023-25345/): Arbitrary local file read vulnerability during template rendering (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-25344 is a critical code injection vulnerability in n/a, published on 15 Mar 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-25344 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-2023-25344/ (Markdown: https://insights.sbomify.com/CVE-2023-25344/index.md)
```

## Sources

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

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