Home

Description

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.

PUBLISHED Reserved 2026-02-19 | Published 2026-02-19 | Updated 2026-02-20 | Assigner VulnCheck




CRITICAL: 9.2CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

HIGH: 8.1CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Problem types

Deserialization of Untrusted Data

Product status

Default status
unaffected

4.4.0 (semver) before 4.4.9
affected

Credits

Dorian Piette (Trachinus) finder

References

blog.spip.net/...-jour-de-securite-sortie-de-SPIP-4-4-9.html vendor-advisory patch

git.spip.net/spip/spip product

www.vulncheck.com/advisories/spip-insecure-deserialization (VulnCheck Advisory: SPIP < 4.4.9 Insecure Deserialization) third-party-advisory

cve.org (CVE-2026-27475)

nvd.nist.gov (CVE-2026-27475)

Download JSON