CVE-2026-22205
Authentication Bypass in SPIP via PHP Type Juggling
Publication date: 2026-02-26
Last updated on: 2026-03-02
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| spip | spip | to 4.4.10 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-288 | The product requires authentication, but the product has an alternate path or channel that does not require authentication. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in SPIP versions prior to 4.4.10 and is caused by PHP type juggling. It allows unauthenticated attackers to bypass authentication by exploiting loose type comparisons in the authentication logic. As a result, attackers can access protected information without proper login verification.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access to sensitive internal data because attackers can bypass login verification without any authentication. This can compromise the confidentiality of protected information and potentially lead to further exploitation or data breaches.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know