# CVE-2022-25271: Improper input validation in Drupal core

> Drupal core form API flaw allows attackers to inject disallowed values or overwrite sensitive data in specific contributed or custom module forms.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** BIT-drupal-2022-25271, CLEANSTART-2024-CD40650, DLA-2925-1, DRUPAL-CORE-2022-003, GHSA-fmfv-x8mp-5767, UBUNTU-CVE-2022-25271

## What is CVE-2022-25271?

CVE-2022-25271 is a high-severity vulnerability in Drupal Drupal, published on 16 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Drupal core's form API has a vulnerability where certain contributed or custom modules' forms may be vulnerable to improper input validation. This could allow an attacker to inject disallowed values or overwrite data. Affected forms are uncommon, but in certain cases an attacker could alter critical or sensitive data.

Weakness: CWE-20 (Improper Input Validation)

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

8 open source packages ship an affected version, including drupal/core and drupal. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | From 7.0.0 | 7.88 |
| `drupal/core` | Packagist | From 7.0.0 | 7.88 |
| `drupal/core` | Packagist | From 8.0.0 | 9.2.13, 9.3.6 |
| `drupal/core` | Packagist | From 8.0.0 | 9.2.13 |
| `drupal/core` | Packagist | From 8.0.0 | 9.2.13 |
| `drupal/core` | Packagist | From 9.3.0 | 9.3.6 |
| `drupal/core` | Packagist | From 9.3.0 | 9.3.6 |
| `drupal` | Bitnami | From 7.0.0 | 7.88.0, 9.2.13, 9.3.6 |

Products: Drupal Drupal, Fedoraproject Fedora.

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

Upgrade drupal/core to a fixed version for your release line: 7.88, 9.2.13 or 9.3.6.

## Is CVE-2022-25271 being exploited?

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

## Other vulnerabilities in Drupal Drupal

- [CVE-2026-9082](https://insights.sbomify.com/CVE-2026-9082/): Drupal Core SQL Injection (critical 9.8, exploited in the wild)
- [CVE-2020-13671](https://insights.sbomify.com/CVE-2020-13671/): Drupal core Un-restricted Upload of File (high 8.8, exploited in the wild)
- [CVE-2019-6340](https://insights.sbomify.com/CVE-2019-6340/): Drupal Core Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2009-3352](https://insights.sbomify.com/CVE-2009-3352/): Other in n/a (critical 10.0)
- [CVE-2024-55636](https://insights.sbomify.com/CVE-2024-55636/): Drupal core - Less critical - Gadget chain - SA-CORE-2024-006 (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25271 is a high-severity vulnerability in Drupal Drupal, published on 16 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25271 in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected from 7.0.0; fixed in 7.88
- drupal/core (Packagist): affected from 7.0.0; fixed in 7.88
- drupal/core (Packagist): affected from 8.0.0; fixed in 9.2.13, 9.3.6
- drupal/core (Packagist): affected from 8.0.0; fixed in 9.2.13
- drupal/core (Packagist): affected from 8.0.0; fixed in 9.2.13
- drupal/core (Packagist): affected from 9.3.0; fixed in 9.3.6
- drupal/core (Packagist): affected from 9.3.0; fixed in 9.3.6
- drupal (Bitnami): affected from 7.0.0; fixed in 7.88.0, 9.2.13, 9.3.6

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

## Sources

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

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