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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/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:XSpip
APPSpip4.4.0 – 4.4.9 (bez)
Related vulnerabilities
SPIP — zdalny command injection przez multipart upload bez uwierzytelnienia
SPIP before 4.2.1 allows Remote Code Execution via form values in the public area because serialization is mis...
SPIP v4.1.5 and earlier was discovered to contain a SQL injection vulnerability via the _oups parameter. This ...
prive/formulaires/configurer_preferences.php in SPIP before 3.2.8 does not properly validate the couleur, disp...
SPIP 3.1.x before 3.1.6 and 3.2.x before Beta 3 does not remove shell metacharacters from the host field, allo...