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

New CVE Detected

CVE-2026-72708 – Unauthenticated Blind SQL Injection – SPIP before 4.4.18

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

Summary

CVE-2026-72708 is an unauthenticated blind SQL injection vulnerability in SPIP, a widely used open-source French CMS, affecting all versions before 4.4.18. The flaw resides in the MySQL escaping logic used by SPIP’s public sitemap generation feature and allows a remote, unauthenticated attacker to extract arbitrary database content. It carries a CVSS v4.0 base score of 8.7 (High).

Technical details

  • Root cause: the MySQL escaper function spip_mysql_cite() in ecrire/req/mysql.php fails to escape a supplied value when the target column is a date-type column and the value matches the pattern of a word character immediately followed by an opening parenthesis. This causes the value to be embedded unescaped into the generated SQL query instead of being treated as a literal.
  • Trigger conditions: the vulnerable code path is reached through the public sitemap template squelettes-dist/sitemap.xml.html, which passes the annee (year) parameter into a date-column query without proper authentication or additional validation.
  • Attack vector: network-based and unauthenticated — an attacker can send a crafted annee value (e.g., a time-based SQL payload) to the public sitemap endpoint of any exposed SPIP site.
  • Impact: successful exploitation enables time-based and boolean-based blind SQL injection, allowing an attacker to enumerate arbitrary database content. This includes exposure of the alea_ephemere secret, which SPIP uses to sign action nonces — potentially enabling further attacks such as CSRF-token/nonce forgery once the secret is recovered.

Affected software

  • SPIP versions prior to 4.4.18 (all versions before 4.4.18 are affected).

Severity

  • CVSS v4.0 Base Score: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: upgrade SPIP to version 4.4.18 or later, where the escaping logic has been fixed.
  • If immediate patching is not possible: restrict or disable public access to the sitemap endpoint (sitemap.xml.html) at the web server or WAF layer, and monitor for anomalous requests containing SQL injection patterns targeting the annee parameter. These are interim measures only — upgrading remains the definitive fix.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge