# CVE-2026-72710: SPIP < 4.4.18 RCE via editer_objet.php Job Queue Injection

> Unauthenticated attackers can achieve remote code execution in SPIP by injecting malicious jobs into the queue via mass assignment in editer_objet.php.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-72710, GHSA-g7qf-5m6v-m9vh, UBUNTU-CVE-2026-72710

## What is CVE-2026-72710?

CVE-2026-72710 is a critical code injection vulnerability in SPIP, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

## Which versions are affected by CVE-2026-72710?


## How do I fix CVE-2026-72710?

Upgrade to a fixed version.

## Is CVE-2026-72710 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72710 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72710 and fix it if it is affected.

What it is: CVE-2026-72710 is a critical code injection vulnerability in SPIP, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72710 exists.

Affected product: SPIP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72710/ (Markdown: https://insights.sbomify.com/CVE-2026-72710/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72710
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72710
- OSV: https://osv.dev/vulnerability/CVE-2026-72710

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72710/
Summaries are generated and may contain mistakes; the official description above is the record.