# CVE-2022-23614: Code injection in Twig

> Attackers can execute arbitrary PHP code via the sort filter in Twig sandbox mode due to improper closure validation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2022
- **Updated:** 23 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-23614, DSA-5107-1, GHSA-5mv2-rx3q-4w2v, UBUNTU-CVE-2022-23614

## What is CVE-2022-23614?

CVE-2022-23614 is a high-severity code injection vulnerability in Debian Debian Linux, published on 4 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Twig is an open source template language for PHP. When in a sandbox mode, the `arrow` parameter of the `sort` filter must be a closure to avoid attackers being able to run arbitrary PHP functions. In affected versions this constraint was not properly enforced and could lead to code injection of arbitrary PHP code. Patched versions now disallow calling non Closure in the `sort` filter as is the case for some other filters. Users are advised to upgrade.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2022-23614?

4 open source packages ship an affected version, including twig/twig. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `twig/twig` | Packagist | From 2.0.0 | 2.14.11 |
| `twig/twig` | Packagist | From 2.0.0 | 2.14.11 |
| `twig/twig` | Packagist | From 3.0.0 | 3.3.8 |
| `twig/twig` | Packagist | From 3.0.0 | 3.3.8 |

Products: Debian Debian Linux, Fedoraproject Fedora, Symfony Twig.

## How do I fix CVE-2022-23614?

Upgrade twig/twig to a fixed version for your release line: 2.14.11 or 3.3.8.

## Is CVE-2022-23614 being exploited?

There is no known exploitation of CVE-2022-23614 in the wild and no public exploit code.

Public exploit code:

- PoC for CVE-2022-23614 (Twig sort filter code execution/sandbox bypass) (github_poc): https://github.com/davwwwx/CVE-2022-23614
- Proof of concept for CVE-2022-23614 (command injection in Twig) (github_poc): https://github.com/4rtamis/CVE-2022-23614

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23614 and fix it if it is affected.

What it is: CVE-2022-23614 is a high-severity code injection vulnerability in Debian Debian Linux, published on 4 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23614 in the wild and no public exploit code.

Affected packages and fixed versions:
- twig/twig (Packagist): affected from 2.0.0; fixed in 2.14.11
- twig/twig (Packagist): affected from 2.0.0; fixed in 2.14.11
- twig/twig (Packagist): affected from 3.0.0; fixed in 3.3.8
- twig/twig (Packagist): affected from 3.0.0; fixed in 3.3.8

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

## Sources

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

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