Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-72710 – Remote Code Execution – SPIP before 4.4.18

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-72710 is a critical remote code execution vulnerability affecting SPIP, an open-source content management system, in versions before 4.4.18. The flaw resides in the editer_objet action, where insufficient validation of the arg parameter allows an attacker holding a valid nonce to inject attacker-controlled rows into the spip_jobs table, leading to arbitrary PHP function execution when the job queue is processed. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical) and a CVSS v4.0 score of 9.3 (Critical).

Technical details

  • Root cause: The editer_objet action resolves SQL table names from the arg parameter without enforcing an allowlist of editable columns/objects (CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes).
  • Trigger conditions: An attacker with a valid nonce can submit arg=job/0 along with crafted fonction and args values, which get written into the spip_jobs table.
  • Attack vector: Network-based (AV:N), requiring no privileges (PR:N) and no user interaction (UI:N); low attack complexity.
  • Impact: When the SPIP cron job queue drains the injected row, the attacker-supplied fonction/args values are unserialized and executed, resulting in arbitrary PHP function execution on the underlying server — full compromise of confidentiality, integrity, and availability.

Affected software

  • SPIP versions prior to 4.4.18 (all earlier versions are affected).
  • Fixed in SPIP 4.4.18 and later.

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Base Score: 9.3 (Critical) — 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

Mitigation and recommended actions

  • Immediate: Upgrade SPIP to version 4.4.18 or later, which enforces proper validation on the editer_objet action and addresses the job queue injection issue.
  • If no patch can be applied immediately: Restrict access to the SPIP private/administrative interface and job-processing endpoints from untrusted networks, monitor the spip_jobs table and job queue processing for unexpected entries, and review server logs for suspicious editer_objet requests referencing arg=job/.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge