Deserialization in Spip
CVE-2026-27475
SPIP before 4.4.9 allows Insecure Deserialization in the public area through the table_valeur filter and the DATA iterator, which accept serialized data. An attacker who can place malicious serialized content (a pre-condition requiring prior access or another vulnerability) can trigger arbitrary object instantiation and potentially achieve code execution. The use of serialized data in these components has been deprecated and will be removed in SPIP 5. This vulnerability is not mitigated by the SPIP security screen.
Vulnerability class: Insecure Deserialization
EPSS: 0.008 (52.1th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
Affected products
- Spip — versions 4.4.0
Weakness classification (CWE)
References
- disclosure@vulncheck.com (vendor-advisory, Release Notes, patch, Vendor Advisory)
- disclosure@vulncheck.com (Product, product)
- disclosure@vulncheck.com (Third Party Advisory, third-party-advisory)
Frequently asked questions
- What is CVE-2026-27475?
- CVE-2026-27475 is a high-severity vulnerability in Spip, classified under Deserialization of Untrusted Data. CVSS score: 8.1/10. Published 2026-02-19.
- How severe is CVE-2026-27475?
- High severity. CVSS v3 base score is 8.1 out of 10.