CVE-2026-72710

SPIP < 4.4.18 RCE via editer_objet.php Job Queue Injection

No known exploitation. EPSS puts it in the 65th percentile. No fix published yet.

CVSS 3.19.8Critical EPSS percentile65th1.1% chance in 30 days CISA KEVNot listedNo confirmed exploitation
No public exploit known FixNone yetNo fix or workaround published

Published 2026-09-11Updated 2026-09-15Sources: CVE.org, NVD

NVD CVE.org

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

Steps

Written by AI from the record

Check whether your website runs SPIP and identify its installed version.
If it is earlier than 4.4.18, schedule an upgrade to SPIP 4.4.18.
After upgrading, have your IT provider review recent administrator activity and unexpected scheduled jobs.

Usually a quick update

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

SPIP versions before 4.4.18 can let an internet attacker take over the website; typical businesses using it should update.

Unauthenticated remote code execution in SPIP’s editer_objet action allows job-queue injection that is executed by the cron worker.

If you're affected

Complete website takeover
Website data theft
Malicious content changes
Service disruption
Ransomware risk

What is it

This is a flaw that can allow a stranger to plant instructions in your website’s background task list. It is like someone slipping a forged work order into your office queue, then having a staff member carry it out as if it were legitimate.

Who is affected

This matters to you if you run a website using SPIP before version 4.4.18. An attacker does not need an account or a staff member to click anything; the risk applies when the SPIP site is reachable from the internet.

How urgent is it

No known public exploit code is on record, and this issue is not listed in CISA’s catalog of vulnerabilities known to be actively exploited. Treat this as an amber priority: arrange the update promptly, especially for internet-facing SPIP sites, but there is no confirmed active-exploitation signal in the findings.

What to do — in detail

Confirm the deployed SPIP version on every production and staging instance, including sites managed by an external host.
Upgrade affected installations from any version before 4.4.18 to SPIP 4.4.18; test the upgrade in a non-production copy first and follow SPIP’s release notes for any application-specific compatibility changes.
If upgrading is delayed, restrict public access to the affected SPIP instance where operationally possible and disable or tightly control access to the vulnerable editing endpoint through a compensating web-server rule.
Review the spip_jobs queue and web-server/application logs for unexpected jobs, unusual PHP function names, or suspicious requests to editer_objet.php; investigate and rotate relevant credentials if compromise is found.
There is no CISA KEV remediation due date because CVE-2026-72710 is not listed in KEV.

Technical context

CVE-2026-72710 is rated CVSS 9.8 (Critical), with network reachability, low attack complexity, no privileges, and no user interaction required. It is CWE-915 mass assignment in SPIP’s editer_objet action: an attacker-controlled arg can target internal SQL tables lacking a champs_editables allowlist, insert a controlled entry into spip_jobs, and obtain RCE when cron executes the queue. CISA KEV does not list the CVE, no public exploit code is on record, and EPSS predicts 0.6% likelihood (48th percentile) with a flat trend.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS65th

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.1% chance of exploitation activity in the next 30 days, which ranks it in the 65th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 7 days, from the signal feeds we watch.

2026-09-18OpenVAS check added
2026-09-15Record updated
2026-09-11Publishedweakness classified, record updated, record updated

Affected products

SPIPoss-project · FR
- SPIPWeb AppOn-premWeb & CMS Plugins / cms-core

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

Attack Vector NetworkExploitable remotely over the network without any special conditions
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required NoneNo authentication required — anyone can exploit this
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity HighTotal loss of integrity — attacker can modify any data in the component
Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

CWE-915No name in the record

Sources

References in the record

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for SPIP, not every advisory.

A free account adds

The full version matrix and every affected product
Exploit links, proofs of concept and Metasploit modules
Email alerts for the products you watch
The same data over REST API, MCP and CLI

Create a free account