SQL Injection in Spip
CVE-2026-122032
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.
Vulnerability class: SQL Injection
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- www.spip.net/fr_article6500.html (patch)
- blog.spip.net/Mise-a-jour-critique-de-securite-sortie-de-SPIP-4-4-29.html (release-notes, issue-tracking)
- www.vulncheck.com/advisories/spip-before-authenticated-sql-injection-via-where-… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-122032?
- CVE-2026-122032 is a medium-severity vulnerability in Spip, classified under SQL Injection. CVSS score: 6.5/10. Published 2026-11-04.
- How severe is CVE-2026-122032?
- Medium severity. CVSS v3 base score is 6.5 out of 10.