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
Published · last modified .
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.
EPSS exploit prediction
EPSS 0.009, 61.2th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Spip — versions 4.4.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- Trachinus/CVE-2026-27475 (last pushed 2026-09-01): PoC for CVE-2026-27475
References
- blog.spip.net/Mise-a-jour-de-securite-sortie-de-SPIP-4-4-9.html (vendor-advisory, Release Notes, patch, Vendor Advisory)
- git.spip.net/spip/spip (Product, product)
- VulnCheck Advisory: SPIP < 4.4.9 Insecure Deserialization (Third Party Advisory, third-party-advisory)
This CVE has public exploit evidence. See the latest CVEs with public exploits.