Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-66738: Authenticated code injection in SQLite-backed SPIP

Published Aug 10, 2026 · Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.7High · v4
EPSS0.67%53rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Spip
IdentifiersCVE-2026-66738CWE-94 · Improper Control of Generation of…

CVE-2026-66738 is a code injection vulnerability in SQLite-backed SPIP installations before version 4.4.18. The navigation menu endpoint improperly handles array-typed user input, allowing it to bypass sanitization and escape an internal quoted string context evaluated as PHP. An authenticated attacker with at least editor (redacteur) privileges can trigger arbitrary operating system command execution through a single crafted GET request. MySQL-backed installations are not affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises confidentiality, integrity, and availability within the access rights of the web server process. An attacker can execute arbitrary commands, access or modify application data and accessible files, and disrupt the application. The vulnerability does not itself establish elevated operating system privileges beyond those of the web server process.

Mitigation

If you can’t patch tonight, do this now.

Until the update is applied, restrict access to editor-capable accounts and limit access to the navigation endpoint. Monitor requests to that endpoint for suspicious activity. Where feasible, migrate affected deployments from SQLite to MySQL, which is not affected.

Remediation

Patch, then assume compromise.

Upgrade SPIP to version 4.4.18 or later. For Debian stable (trixie), update the spip package to version 4.4.19+dfsg-0+deb13u1 or a later security-fixed package.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2026-66738-POCThe repository contains a standalone authenticated command-execution exploit, a reproducible lab recipe, and supplied comparison logs. Its 10 files comprise three executable scripts (two Python and one Bash), a Dockerfile, Docker Compose configuration, README, license, ignore file, and two evidence logs. No exploit framework is used. The supplied file sizes total 27,469 bytes; the repository URL, revision, and actual archive size were not supplied, so their fields use empty or zero placeholders. poc.py uses only Python's standard library. It parses the SPIP login form, submits operator-provided credentials, maintains cookies, and sends a crafted GET to /ecrire/?exec=navigation. The two menu array elements exploit a documented mismatch between SQLite string quoting and PHP expression construction: a trailing backslash changes PHP quote interpretation, allowing the following element to become executable PHP in an eval-backed DATA-loop filter. PHP backticks run the requested shell command and print its output into the response. This is code injection rather than a conventional SQL-injection data-extraction payload. The repository reports SQLite installations before 4.4.18 as affected and MySQL installations as unaffected; those release and advisory claims were not independently verified. The Dockerfile builds PHP 8.4/Apache with SQLite support and downloads stock SPIP. Compose provides separate 4.4.16 vulnerable and 4.4.18 control profiles on host ports 8091 and 8092. setup/install-lab.py drives the web installer and provisions an administrator and an editor through normal forms; setup/install.sh supplies fixed lab credentials. Account creation is lab setup, not part of the exploitation payload. The supplied Dockerfile does not explicitly install Python 3 despite the provisioning script requiring it, so container provisioning may require correction. The vulnerable evidence log reports nine injected id outputs; the fixed control reports none. These are supplied artifacts, not independently reproduced results. README sample counts differ from the stored logs. Reported root execution reflects the described test namespace, not an inherent privilege-escalation capability: normal execution inherits the web-server account. Success detection searches for a marker after removing data-origin attributes and may mistake other reflected payload text for execution. Other limitations include no TLS support, ignored base-URL path prefixes, and no enforcement of the documented single-quote restriction. No fixed external command-and-control or exfiltration endpoint is present.fixedbyreboot · Disclosed Nov 10, 2026 · python · bash · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SpipSpipapplication
FAQ

Frequently asked questions

Is CVE-2026-66738 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-66738 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-66738?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-66738, the earliest disclosed Nov 10, 2026.
Is there a patch for CVE-2026-66738?
Upgrade SPIP to version 4.4.18 or later. For Debian stable (trixie), update the spip package to version 4.4.19+dfsg-0+deb13u1 or a later security-fixed package.
What products are affected by CVE-2026-66738?
Spip.
How severe is CVE-2026-66738?
CVE-2026-66738 has a CVSS v4 score of 7.7 (High) and an EPSS score of 0.67% (53rd percentile) as of Nov 17, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.