CVE-2026-122032: SPIP · SQL Injection
Affects SPIPSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 4.4.29 soon.
Data as of 4 Nov 2026, 15:43 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.1 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 6.5 |
- Patch
- Available – fixed in 4.4.29
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade SPIP to 4.4.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SPIPSPIP | Affected
| Fixed in
|
AI-suggested
Upgrade SPIP to version 4.4.29 or later, where this SQL injection vulnerability has been fixed. No other mitigations are indicated by the vendor advisory.
Description
SPIP versions prior to 4.4.29 contain a SQL injection vulnerability that allows authenticated users with back-office access to inject arbitrary SQL commands by exploiting a mismatch between POST and GET parameters on the /ecrire/?exec=articles endpoint. This flaw bypasses the sanitization function spip_sanitize_from_request(), enabling attackers to extract sensitive database information, including protected articles and bcrypt password hashes. The vulnerability is rated high severity with a CVSS 4.0 score of 7.1. A fix is available in SPIP version 4.4.29.