CVE-2026-22205 json
SPIP < 4.4.10 Authentication Bypass via PHP Type Juggling
published 8mo ago modified 4mo ago also EUVD-2026-8883
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
SPIP versions prior to 4.4.10 contain an authentication bypass vulnerability caused by PHP type juggling that allows unauthenticated attackers to access protected information. Attackers can exploit loose type comparisons in authentication logic to bypass login verification and retrieve sensitive internal data.
Patch / fix
- SPIP SPIP 4.4.10
- spip Debian 13 4.4.11+dfsg-0+deb13u1
- spip Debian 14 4.4.10+dfsg-1
debian advisories DEBIAN-CVE-2026-22205
Is CVE-2026-22205 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8mo ago
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- SPIP SPIP
Classification
- Weakness
-
- CWE-288 Authentication Bypass Using an Alternate Path or Channel
References
-
blog.spip.net
/Mise-a-jour-de-securite-sortie-de-SPIP-4-4-10.html
vendor-advisory, patch, release-notes
-
git.spip.net
/spip/spip
product
-
vulncheck.com
/advisories/spip-sql-injection-rce-via-union-php-tags
related, third-party-advisory
Sources
- CVE List CVE-2026-22205
- NVD CVE-2026-22205
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.