SPIP <= 4.4.17 Remote Code Execution Vulnerability: Early Warning
- Severity
- CRITICAL
- CVSS
- 9.8
- Affected component
- spip (other)
- Patched version
- 4.4.18
An early warning has been issued for a critical remote code execution vulnerability in SPIP versions prior to 4.4.18. This vulnerability, tracked as CVE-2026-72710, allows attackers to inject arbitrary PHP functions into the spip_jobs table, potentially leading to system compromise.
What happened
SPIP versions prior to 4.4.18 reportedly contain a remote code execution vulnerability in the editer_objet action. Attackers can exploit this vulnerability by injecting attacker-controlled rows into the spip_jobs table, which can result in the execution of arbitrary PHP functions on the underlying system. This vulnerability is under investigation and has not yet been exploited in the wild.
The vulnerability was first flagged on 2026-09-11T17:18:58.907000+00:00. The CVSS score is 9.8, indicating a critical severity level. The National Vulnerability Database (NVD) has assigned CVE-2026-72710 to this issue.
What to do about it
- Upgrade SPIP to version 4.4.18 or later to mitigate the remote code execution vulnerability.
- Review your system for any signs of unauthorized activity or injected rows in the spip_jobs table.
- Monitor the NVD and other primary sources for updates on this vulnerability.
- Consider implementing additional security measures to protect against potential exploitation, such as restricting access to the editer_objet action.
How 0Day would have caught this
spip is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
If you are using SPIP version 4.4.17 or earlier, you are potentially affected by this vulnerability. Upgrade to version 4.4.18 or later to mitigate the risk.
What should I do right now?
Immediately upgrade SPIP to version 4.4.18 or later. Monitor your system for any signs of unauthorized activity and consult the primary sources for further updates.
Is there an official fix available?
Yes, the official fix is to upgrade to SPIP version 4.4.18 or later.
Should I be concerned about this vulnerability?
Yes, given the critical severity and potential for remote code execution, it is important to take immediate action to upgrade and monitor your system.