Critical severity · published Sep 11, 2026
CVE-2026-72710
SPIP < 4.4.18 RCE via editer_objet.php Job Queue Injection
9.8
CVSS
1.1%
EPSS
No
On KEV
Description
SPIP before 4.4.18 contains a mass assignment vulnerability in the editer_objet action that allows unauthenticated attackers to write arbitrary rows to any SQL table lacking a champs_editables allowlist by supplying an attacker-controlled arg parameter resolving to internal database tables. Attackers can insert a malicious row into the spip_jobs queue with a controlled PHP function and arguments, which is then dynamically executed when the cron processes the queue, resulting in remote code execution.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.1% · higher than 66% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SP
SPIP · SPIP
before 4.4.18 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72710
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-72710
technical-description
https://blog.lexfo.fr/casse-spip-sqli-to-rce.html
release-notes
https://blog.spip.net/Mise-a-jour-critique-de-securite-sortie-de-SPIP-4-4-18.html
third-party-advisory
https://www.vulncheck.com/advisories/spip-remote-code-execution-via-editer-objet-php-job-queue-injection
More from SPIP
9.8
CVE-2026-72709
SPIP < 4.4.18 Missing Authorization via ecrire/action/
9.8
CVE-2026-77806
SPIP before 4.4.21 allows unauthenticated remote attackers to execute arbitrary code, as exploited in the wild in August 2026
9.8
CVE-2026-77647
SPIP before 4.4.20 allows unauthenticated remote attackers to execute arbitrary code, as exploited in the wild in August 2026
9.8
CVE-2024-8517
SPIP Bigup Multipart File Upload OS Command Injection
9.8
CVE-2023-27372
SPIP before 4.2.1 allows Remote Code Execution via form values in the public area because serialization is mishandled
