CVE-2025-71250: Critical severity Spip SPIP vulnerability
Published Feb 19, 2026
·Updated
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Affected Software
1 affected component
Spip SPIP<4.4.9
Event History
Feb 19, 2026
CVE Published
via MITRE·02:58 PM
Rejected
via MITRE·02:58 PM
Data Sourced
via NVD·04:27 PM
Description
Rejected
via MITRE·06:39 PM
Frequently Asked Questions
1
What is the severity of CVE-2025-71250?
The severity of CVE-2025-71250 is classified as critical due to the potential for arbitrary object deserialization leading to remote code execution.
2
How do I fix CVE-2025-71250?
To fix CVE-2025-71250, upgrade SPIP to version 4.4.9 or later.
3
What are the potential impacts of CVE-2025-71250?
The potential impacts of CVE-2025-71250 include unauthorized access, data manipulation, and remote code execution if exploited.
4
Who is affected by CVE-2025-71250?
CVE-2025-71250 affects all SPIP installations prior to version 4.4.9 that utilize the table_valeur filter and DATA iterator.
5
What does CVE-2025-71250 vulnerability entail?
CVE-2025-71250 involves insecure deserialization allowing attackers to send malicious serialized content to trigger arbitrary actions.