# CVE-2023-29689: PyroCMS remote code execution vulnerability

> Attackers can execute arbitrary code on PyroCMS servers via server-side template injection, requiring immediate patching.

- **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 Aug 2023
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-w7vm-4v3j-vgpw

## What is CVE-2023-29689?

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

### Official description

PyroCMS 3.9 contains a remote code execution (RCE) vulnerability that can be exploited through a server-side template injection (SSTI) flaw. This vulnerability allows a malicious attacker to send customized commands to the server and execute arbitrary code on the affected system.

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

2 open source packages ship an affected version, including pyrocms/pyrocms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyrocms/pyrocms` | Packagist | All versions to 3.9 | None |
| `pyrocms/pyrocms` | Packagist | All versions to 3.9 | None |

Products: Pyrocms Pyrocms.

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

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

## Is CVE-2023-29689 being exploited?

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

Public exploit code:

- Pyro CMS 3.9 - Server-Side Template Injection (SSTI) (Authenticated) (exploitdb)
- A drop-in fix for CVE-2023-29689 - SSTI in PyroCMS, via a custom Twig Sandbox implementation (github_poc): https://github.com/YSaxon/pyrocms-ssti-fix

## Other vulnerabilities in n/a

- [CVE-2022-37721](https://insights.sbomify.com/CVE-2022-37721/): PyroCMS vulnerable to stored Cross Site Scripting (critical 9.0)
- [CVE-2020-25263](https://insights.sbomify.com/CVE-2020-25263/): PyroCMS Vulnerable to CSRF (high 7.1)
- [CVE-2022-35118](https://insights.sbomify.com/CVE-2022-35118/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-58297](https://insights.sbomify.com/CVE-2024-58297/): PyroCMS v3.0.1 Stored Cross-Site Scripting via Admin Redirects (medium 5.3)
- [CVE-2020-25262](https://insights.sbomify.com/CVE-2020-25262/): PyroCMS Vulnerable to CSRF (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29689 is a critical code injection vulnerability in n/a, published on 4 Aug 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-29689 exists.

Affected packages and fixed versions:
- pyrocms/pyrocms (Packagist): affected all versions up to 3.9; no fix listed
- pyrocms/pyrocms (Packagist): affected all versions up to 3.9; 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-29689/ (Markdown: https://insights.sbomify.com/CVE-2023-29689/index.md)
```

## Sources

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

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