# CVE-2026-122032: SPIP before 4.4.29 Authenticated SQL Injection via where Parameter


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-122032, GHSA-hjqm-w8hv-xfp6, UBUNTU-CVE-2026-122032

## What is CVE-2026-122032?

CVE-2026-122032 is a high-severity vulnerability in SPIP, published on 4 Nov 2026. 

### Official description

SPIP before 4.4.29 contains a SQL injection vulnerability that allows authenticated attackers with back-office access to inject arbitrary SQL by submitting a differing where parameter value in the POST body versus the GET query string on the /ecrire/?exec=articles endpoint, bypassing spip_sanitize_from_request() sanitization. Attackers can exploit this request parameter mismatch to extract database contents, including protected articles and bcrypt password hashes of users.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-122032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122032 is a high-severity vulnerability in SPIP, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122032 in the wild and no public exploit code.

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

## Sources

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

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