# CVE-2022-23601: CSRF token missing in Symfony

> Symfony form component fails to enable CSRF protection by default, allowing attackers to perform cross-site request forgery attacks against applications using the framework.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Feb 2022
- **Updated:** 23 Apr 2025
- **Also known as:** BIT-symfony-2022-23601, GHSA-vvmr-8829-6whx

## What is CVE-2022-23601?

CVE-2022-23601 is a high-severity vulnerability in Sensiolabs Symfony, published on 1 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. The Symfony form component provides a CSRF protection mechanism by using a random token injected in the form and using the session to store and control the token submitted by the user. When using the FrameworkBundle, this protection can be enabled or disabled with the configuration. If the configuration is not specified, by default, the mechanism is enabled as long as the session is enabled. In a recent change in the way the configuration is loaded, the default behavior has been dropped and, as a result, the CSRF protection is not enabled in form when not explicitly enabled, which makes the application sensible to CSRF attacks. This issue has been resolved in the patch versions listed and users are advised to update. There are no known workarounds for this issue.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

7 open source packages ship an affected version, including symfony/framework-bundle and symfony. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `symfony/framework-bundle` | Packagist | From 5.3.14 | 5.3.15 |
| `symfony/framework-bundle` | Packagist | From 5.3.14 | 5.3.15 |
| `symfony/framework-bundle` | Packagist | From 5.4.3 | 5.4.4 |
| `symfony/framework-bundle` | Packagist | From 5.4.3 | 5.4.4 |
| `symfony/framework-bundle` | Packagist | From 6.0.3 | 6.0.4 |
| `symfony/framework-bundle` | Packagist | From 6.0.3 | 6.0.4 |
| `symfony` | Bitnami | All versions | 5.3.15, 5.4.4, 6.0.4 |

Products: Sensiolabs Symfony.

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

Upgrade symfony/framework-bundle to a fixed version for your release line: 5.3.15, 5.4.4 or 6.0.4.

## Is CVE-2022-23601 being exploited?

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

## Other vulnerabilities in Sensiolabs Symfony

- [CVE-2019-11325](https://insights.sbomify.com/CVE-2019-11325/): Improper Input Validation in Symfony (critical 9.8)
- [CVE-2017-11365](https://insights.sbomify.com/CVE-2017-11365/): Symfony Incorrect Access Control (critical 9.8)
- [CVE-2019-10913](https://insights.sbomify.com/CVE-2019-10913/): Invalid HTTP method overrides allow possible XSS or other attacks in Symfony (critical 9.8)
- [CVE-2018-11407](https://insights.sbomify.com/CVE-2018-11407/): Symfony Authentication Bypass (critical 9.8)
- [CVE-2016-2403](https://insights.sbomify.com/CVE-2016-2403/): Symfony Authentication Bypass (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23601 is a high-severity vulnerability in Sensiolabs Symfony, published on 1 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-23601 in the wild and no public exploit code.

Affected packages and fixed versions:
- symfony/framework-bundle (Packagist): affected from 5.3.14; fixed in 5.3.15
- symfony/framework-bundle (Packagist): affected from 5.3.14; fixed in 5.3.15
- symfony/framework-bundle (Packagist): affected from 5.4.3; fixed in 5.4.4
- symfony/framework-bundle (Packagist): affected from 5.4.3; fixed in 5.4.4
- symfony/framework-bundle (Packagist): affected from 6.0.3; fixed in 6.0.4
- symfony/framework-bundle (Packagist): affected from 6.0.3; fixed in 6.0.4
- symfony (Bitnami): affected all versions; fixed in 5.3.15, 5.4.4, 6.0.4

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

## Sources

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

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