# CVE-2026-22206: SPIP < 4.4.10 SQL Injection RCE via Union & PHP Tags

> Authenticated low-privilege users can achieve remote code execution via SQL injection and PHP tag processing in SPIP.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 26 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** DEBIAN-CVE-2026-22206, GHSA-48x6-97gc-jx62, UBUNTU-CVE-2026-22206

## What is CVE-2026-22206?

CVE-2026-22206 is a high-severity SQL injection vulnerability in Spip Spip, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SPIP versions prior to 4.4.10 contain a SQL injection vulnerability that allows authenticated low-privilege users to execute arbitrary SQL queries by manipulating union-based injection techniques. Attackers can exploit this SQL injection flaw combined with PHP tag processing to achieve remote code execution on the server.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-22206?

It affects 1 product.


Products: Spip Spip.

## How do I fix CVE-2026-22206?

Upgrade to a fixed version.

## Is CVE-2026-22206 being exploited?

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

## Other vulnerabilities in Spip Spip

- [CVE-2012-4331](https://insights.sbomify.com/CVE-2012-4331/): Other in n/a (critical 10.0)
- [CVE-2008-5812](https://insights.sbomify.com/CVE-2008-5812/): Other in n/a (critical 10.0)
- [CVE-2024-8517](https://insights.sbomify.com/CVE-2024-8517/): SPIP Bigup Multipart File Upload OS Command Injection (critical 9.8)
- [CVE-2023-24258](https://insights.sbomify.com/CVE-2023-24258/): SQL injection in n/a (critical 9.8)
- [CVE-2017-9736](https://insights.sbomify.com/CVE-2017-9736/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22206 and fix it if it is affected.

What it is: CVE-2026-22206 is a high-severity SQL injection vulnerability in Spip Spip, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22206 in the wild and no public exploit code.

Affected product: Spip Spip. 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-2026-22206/ (Markdown: https://insights.sbomify.com/CVE-2026-22206/index.md)
```

## Sources

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

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