Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify internet-facing SPIP <4.4.21
-
DeliverySend GET with newline-injected parameter
-
ExploitInject X-Spip-Filtre header into compiled template
-
Executionanalyse_resultat_skel runs intval|_request|system filter chain
-
PersistRead shell command from POST parameter 0
-
ImpactExecute commands as web-server user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions - remote unauthenticated exploitation against default configurations of SPIP versions below 4.4.21; the vulnerable analyse_resultat_skel() template processing is core functionality, not an optional feature. The concrete prerequisite is simply a reachable SPIP endpoint (e.g. spip.php) that renders templates, which is the normal operating state of the CMS. Limiting factors are minimal: the target must be running an affected version (<4.4.21) on a Unix/Linux PHP host, and the injected commands execute with the privileges of the web-server user (the Metasploit run shows the shell as user 'jvoisin', i.e. non-root/'Privileged' => false), so impact is bounded by that account's permissions absent further privilege escalation. |
| Impact | This is a genuine high-priority issue, not an inflated CVSS score. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H, base 9.8) indicates unauthenticated network exploitation with low complexity and full impact, and that assessment is corroborated by a functional, publicly available Metasploit module demonstrating an interactive shell - the two strongest independent signals align. The CVE description asserts active in-the-wild exploitation in August 2026, but this is NOT independently confirmed via CISA KEV in the supplied data, so it should be treated as a strong claim pending KEV/vendor confirmation rather than established fact. No EPSS score and no SSVC decision data were provided, so probability-of-exploitation and automatability cannot be quantified from this input; however, the existence of weaponized exploit code effectively removes the barrier to exploitation regardless. Any organization running an internet-facing SPIP instance below 4.4.21 should treat this as an emergency patch, since the exploit requires no credentials and no user interaction. |
| Exploit ScenarioDerived | An attacker sends a single crafted HTTP GET request to spip.php with a newline-embedded parameter value that injects header("X-Spip-Filtre: intval|_request|system"), plus a POST parameter '0' carrying an OS command; SPIP compiles this into its template, executes the filter chain, and runs the command as the web-server user, returning a shell. A public Metasploit module (exploit/multi/http/spip_x_spip_filtre_rce) fully automates this, including an autocheck that invokes phpinfo() to confirm vulnerability. Because AV:N/AC:L/PR:N/UI:N, no authentication, victim interaction, or special network position is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 21, 2026
Remote code execution in SPIP CMS versions prior to 4.4.21 lets unauthenticated attackers run arbitrary PHP/OS commands by abusing the template engine's X-Spip-Filtre header handling. A newline injected into a GET parameter forces analyse_resultat_skel() to treat an attacker-supplied header() call as a template filter chain, and a working Metasploit module (intval|_request|system) already achieves full command shell access. The CVE description claims in-the-wild exploitation in August 2026; publicly available exploit code exists, making this a top-priority patch.
RemediationAI
Vendor-released patch: upgrade to SPIP 4.4.21, which fixes the analyse_resultat_skel() header mishandling, per the vendor advisory at https://blog.spip.net/Mise-a-jour-critique-de-securite-sortie-de-SPIP-4-4-21.html. Upgrade is the primary and recommended action given a public exploit exists. If an immediate upgrade is impossible, apply compensating controls: place the SPIP application behind a WAF/reverse proxy rule that strips or rejects any request whose GET/POST parameter values contain newline (CR/LF) characters, and block or filter requests that attempt to inject an X-Spip-Filtre token into parameter values - note this can break legitimate multi-line form input and requires tuning to avoid false positives. Restrict public access to the SPIP site (IP allow-listing or authentication at the proxy) until patched, accepting the availability trade-off of reduced public reachability. After patching, review web/access logs for prior exploitation, as the Metasploit module notes IOC_IN_LOGS side effects.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SPIP is a PHP-based content management/publishing system whose template ('squelette'/skel) engine compiles pages into PHP. The flaw is a CWE-94 code injection: analyse_resultat_skel() scans the rendered page body for <?php header("X-Spip-Filtre: ..."); ?> patterns and invokes each listed name as a template filter function. Because a raw newline in a GET parameter value is carried into the compiled PHP template, an attacker can inject their own header() call and thereby name arbitrary PHP functions as filters. The demonstrated chain intval|_request|system collapses the page body to '0', uses SPIP's _request() to read the POST parameter named '0' (the command), and passes it to system() for execution. Affected component per CPE is cpe:2.3:a:spip:spip:*:*:*:*:*:*:*:* (all versions below 4.4.21).
Know when Spip gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated (PR:N) network RCE via a single crafted request with no user interaction (AV:N/AC:L/UI:N), yielding full command execution as the web user (C:H/I:H/A:H, scope unchanged).
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
2DescriptionCVE.org
SPIP before 4.4.21 allows unauthenticated remote attackers to execute arbitrary code, as exploited in the wild in August 2026. This is related to code injection via an X-Spip-Filtre HTTP request header that is mishandled by analyse_resultat_skel.
Latest POC
1 public PoC link from nuclei
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
SPIP CMS versions prior to 4.4.21 contain a critical remote code execution vulnerability exploitable by unauthenticated attackers. Publicly available exploit code enables complete command-line access to affected systems without requiring authentication. Organizations using SPIP must patch immediately to prevent unauthorized system compromise.
Apply vendor patch.
Threat Model
5 threats: Elevation of Privilege, Tampering, Information Disclosure and 1 more
3-step attack chain with trust boundaries and controls
Full threat model - attack chain, trust boundaries, controls per stage and evidence - is part of the Pro and Business plans.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
The Saisies plugin for SPIP CMS versions 5.4.0 through 5.11.0 contains a critical remote code execution vulnerability. A
The Security Screen (_core_/securite/ecran_securite.php) before 1.1.8 for SPIP, as used in SPIP 3.0.x before 3.0.12, all
Cross-site scripting (XSS) vulnerability in valider_xml.php in SPIP 3.1.2 and earlier allows remote attackers to inject
Directory traversal vulnerability in ecrire/exec/valider_xml.php in SPIP 3.1.2 and earlier allows remote attackers to en
The SPIP template composer/compiler in SPIP 3.1.2 and earlier allows remote authenticated users to execute arbitrary PHP
Remote code execution in SPIP before 4.4.20 allows unauthenticated attackers to run arbitrary PHP on the server by explo
SPIP before 4.3.2, 4.2.16, and 4.1.18 is vulnerable to a command injection issue. Rated critical severity (CVSS 9.8), th
SPIP before 4.2.1 allows Remote Code Execution via form values in the public area because serialization is mishandled. R
SPIP 3.0.x before 3.0.9, 2.1.x before 2.1.22, and 2.0.x before 2.0.23 allows remote attackers to gain privileges and "ta
Unauthenticated SQL injection in SPIP referer_spam plugin before 1.3.0 via the referrer tracking functionality. PoC and
SPIP v4.1.5 and earlier was discovered to contain a SQL injection vulnerability via the _oups parameter. Rated critical
Remote code execution in the SPIP CMS (all versions before 4.4.18) lets attackers holding a valid nonce inject rows into
EUVD-2026-63948
GHSA-vgr8-rqwx-wqrp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB