CVE Tools

CVE-2026-72708

SPIP < 4.4.18 Unauthenticated Blind SQL Injection via sitemap.xml.html

No known exploitation. EPSS puts it in the 42nd percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

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
  1. Check whether your website runs SPIP and confirm its installed version.
  2. If it is earlier than 4.4.18, schedule an upgrade to SPIP 4.4.18.
  3. Until the upgrade is complete, have your web host restrict public requests to sitemap.xml.html if this does not disrupt your site.
  4. After updating, ask IT to review web-server logs for unusual requests to sitemap.xml.html.

What it is

From the CVE record

SPIP before 4.4.18 contains an unauthenticated blind SQL injection vulnerability in the SQL escaping layer that allows unauthenticated attackers to inject arbitrary SQL by supplying a crafted annee parameter value matching a word character followed by an open parenthesis, which bypasses escaping for date-type columns across MySQL, SQLite, and PostgreSQL backends. Attackers can exploit the always-present sitemap.xml.html template's annee criterion to embed unescaped time-based or boolean payloads into database queries, enabling extraction of arbitrary database content including the alea_ephemere secret used to sign SPIP action nonces.

In plain language

Written by AI from the record

SPIP versions before 4.4.18 let an outsider read sensitive database information without signing in, so affected businesses should update soon.

Unauthenticated blind SQL injection in SPIP’s date-column escaping can be triggered through the always-present sitemap.xml.html template’s crafted annee parameter.

If you're affected

  • Sensitive database data exposure
  • Secret key disclosure
  • Possible account-action forgery
  • Privacy incident risk

Exploitation

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

EPSS42nd
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

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 42nd percentile of scored CVEs.

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

Lifecycle

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

  1. OpenVAS check added
  2. Record updatedrecord updated
  3. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

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

Scored 7.5 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 NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

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.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store