Skip to navigation

Threat reportVulnerabilityTL-2026-2221

Pre-Authentication Remote Code Execution in SPIP CMS (CVE-2026-77806) — Actively Exploited

criticalACTIVE

SPIP versions before 4.4.21 contain a universal, pre-authentication remote code execution vulnerability (CVE-2026-77806, CVSS 9.8) in which the analyse_resultat_skel() template function mishandles an attacker-supplied X-Spip-Filtre HTTP header, letting an unauthenticated attacker chain PHP filter functions (e.g. intval|_request|system) to execute arbitrary OS commands. First disclosed .

Key facts

IdentifiersTL-2026-2221, CVE-2026-77806, CVE-2026-77647
SeverityCRITICAL
CVSS9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
First disclosed
EPSSCVE-2026-77806: 4.2% (90.2th percentile); CVE-2026-77647: 0.8% (54.3th percentile)
Affected productsSPIP SPIP CMS
Weaknesses (CWE)CWE-94
ToolsMetasploit module multi/http/spip_x_spip_filtre_rce
MITRE ATT&CK techniquesT1059 Command and Scripting Interpreter, T1071 Application Layer Protocol, T1190 Exploit Public-Facing Application, T1588 Obtain Capabilities, T1590 Gather Victim Network Information, T1592 Gather Victim Host Information, T1595 Active Scanning
MotivationUNKNOWN
Target regionsGlobal
Detection rules9 (1 shown free)
Sources14 cited sources

Detection coverage

As of 2026-08-29, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2221 across Splunk SPL, Microsoft KQL and Sigma, covering 8 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: SPIP CVE-2026-77806 — Web Process Spawning Shell via system() Filter Chain (SPL)

Detects the post-exploitation command-execution stage of CVE-2026-77806: a PHP/web-server process (php-fpm, php-cgi, apache2, httpd, nginx) spawning a command interpreter, consistent with the exploit's intval|_request|system filter chain — where intval() collapses the response to '0', _request() re-reads a POST parameter literally named '0' holding the attacker's shell command, and system() executes it. Also covers the fact that this bypasses SPIP's built-in security screen (ecran de securite), so successful post-exploitation activity will not be blocked by that layer.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1059, T1059.004, T1211, T1588.005
  • Data sources: sysmon, linux_auditd, edr_process_telemetry
  • Severity: critical
  • Confidence: high

Splunk SPL

index=sysmon OR index=edr sourcetype IN ("XmlWinEventLog:Microsoft-Windows-Sysmon/Operational","linux:auditd","linux:process") (EventCode=1 OR type=EXECVE)
| eval parent=coalesce(ParentImage, parent_process_name)
| where match(parent, "(?i)(php-fpm|php-cgi|apache2|httpd|nginx|spip)")
| eval child=coalesce(Image, process_exec)
| where match(child, "(?i)(/bin/sh|/bin/bash|/bin/dash|cmd\.exe|powershell\.exe)")
| eval cmdline=coalesce(CommandLine, process_command_line)
| where match(cmdline, "(?i)(whoami|uname|wget |curl |base64 -d|/etc/passwd|id;| id )") OR isnotnull(cmdline)
| stats count min(_time) as first_seen max(_time) as last_seen values(cmdline) as commands by host, parent, child, user
| where count > 0

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName in~ ("php-fpm", "php-cgi", "apache2", "httpd", "nginx", "w3wp.exe")
| where FileName in~ ("sh", "bash", "dash", "cmd.exe", "powershell.exe")
| where ProcessCommandLine has_any ("whoami", "uname", "wget ", "curl ", "base64 -d", "/etc/passwd", " id ")
| project Timestamp, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, AccountName
| order by Timestamp desc

Sigma

title: Web Server Process Spawning Shell Following SPIP RCE Filter Chain Execution
id: 3a7d9c15-2e6f-4b81-a9d4-7f0c3e5b8a92
status: experimental
description: Detects a PHP/web-server process (php-fpm, apache2, httpd, nginx) spawning a command interpreter shortly after an attacker-supplied X-Spip-Filtre filter chain (intval|_request|system) is invoked, consistent with post-exploitation command execution for CVE-2026-77806. This activity is not caught by SPIP's built-in security screen (ecran de securite).
references:
    - https://blog.spip.net/Mise-a-jour-critique-de-securite-sortie-de-SPIP-4-4-21.html
    - https://github.com/rapid7/metasploit-framework/pull/21790
author: Threadlinqs Team
date: 2026/08/29
tags:
    - attack.execution
    - attack.t1059
    - attack.t1059.004
    - attack.defense-evasion
    - attack.t1211
    - cve.2026.77806
    - attack.tool.metasploit
logsource:
    category: process_creation
    product: linux
detection:
    selection_parent:
        ParentImage|contains:
            - 'php-fpm'
            - 'php-cgi'
            - 'apache2'
            - 'httpd'
            - 'nginx'
    selection_child:
        Image|endswith:
            - '/sh'
            - '/bash'
            - '/dash'
    filter_indicators:
        CommandLine|contains:
            - 'whoami'
            - 'uname'
            - 'wget '
            - 'curl '
            - 'base64 -d'
            - '/etc/passwd'
    condition: selection_parent and selection_child and filter_indicators
falsepositives:
    - Legitimate PHP application shell-outs (rare on hardened SPIP deployments); CI/CD or hosting-provider maintenance scripts invoking a shell from the web-server account
level: critical

Known false positives:

  • Hosting-provider automation, backup agents, or CI/CD deployment scripts that legitimately shell out from the web-server service account; baseline and allowlist known maintenance process trees

Tuning notes: Baseline your environment's legitimate php-fpm/apache-to-shell child-process pairs (e.g. known cron wrappers or deploy hooks) and exclude those specific command-line patterns; keep the alert on any command containing recon primitives like whoami/uname/id.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • SPIP CVE-2026-77806 — X-Spip-Filtre Header / Forum Texte PHP Filter Chain Injection (KQL) · unlock with TL Creds
  • SPIP CVE-2026-77806 — Web Process Spawning Shell via system() Filter Chain (KQL) · unlock with TL Creds
  • SPIP CVE-2026-77806 — Outbound C2 Callback / Second-Stage Payload Retrieval from Exploited Host (KQL) · unlock with TL Creds
  • SPIP CVE-2026-77806 — X-Spip-Filtre Header / Forum Texte PHP Filter Chain Injection (Sigma) · unlock with TL Creds
  • SPIP CVE-2026-77806 — Web Process Spawning Shell via system() Filter Chain (Sigma) · unlock with TL Creds
  • SPIP CVE-2026-77806 — Outbound C2 Callback / Second-Stage Payload Retrieval from Exploited Host (Sigma) · unlock with TL Creds
  • SPIP CVE-2026-77806 — X-Spip-Filtre Header / Forum Texte PHP Filter Chain Injection (SPL) · unlock with TL Creds
  • SPIP CVE-2026-77806 — Outbound C2 Callback / Second-Stage Payload Retrieval from Exploited Host (SPL) · unlock with TL Creds

Indicators of compromise

As of 2026-08-29, Threadlinqs Intelligence tracks 8 indicators of compromise for TL-2026-2221.

8 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

The flaw is not mitigated by SPIP's built-in security screen and CERT-FR, SPIP, and multiple vulnerability trackers confirm exploitation attempts in the wild during August 2026; a public Metasploit module was merged 2026-08-24.

SPIP is a widely deployed open-source French CMS used heavily by government, media, and nonprofit sites. On 2026-08-17, SPIP shipped 4.4.20 as an emergency fix for CVE-2026-77647 — a code-injection flaw caused by incorrect identification of <?php blocks and var_export()'s mishandling of a leading '<' character, also reported anonymously via ANSSI and also exploited in the wild before 4.4.20. That patch proved incomplete: on 2026-08-20 SPIP released 4.4.21 to fix a second, related pre-authentication RCE, CVE-2026-77806.

CVE-2026-77806's root cause is a function-call injection flaw in analyse_resultat_skel(), the core SPIP template-rendering function. When a compiled template body contains a `<?php header("X-Spip-Filtre: ..."); ?>` marker, the colon-delimited function names found there are invoked as a chain of PHP filters against the reachable output — but SPIP fails to prevent an attacker from supplying that marker's value directly via the real HTTP request's X-Spip-Filtre header, and from steering user-controlled text into the compiled template body in the first place. The documented path to that compiled body is the forum-preview feature: an unauthenticated visitor's submission to the public forum "texte" field is rendered through the vulnerable skeleton compiler (reachable via endpoints such as ecrire/?exec=forum), giving an attacker a route to the sink without any account or session. The publicly available Metasploit module (multi/http/spip_x_spip_filtre_rce, rapid7/metasploit-framework PR #21790, authored by Julien Voisin/jvoisin, merged 2026-08-24) demonstrates the exploitation primitive: the filter chain `intval|_request|system` first collapses the response body to the string "0" via intval(), then _request() re-reads a POST parameter literally named "0" containing an attacker-supplied OS command string, which system() then executes — yielding unauthenticated, unattended remote code execution with a single crafted HTTP request. The module supports delivery via GET parameter injection, a forum POST to the texte field, or newline injection to smuggle the header value into the request, and was validated against SPIP 4.4.19 and 4.4.20.

Critically, both the CERT-FR advisory and the SPIP vendor bulletin state that this flaw is NOT caught by SPIP's built-in "security screen" (écran de sécurité) — the CMS's dedicated input-filtering defense layer that normally screens malicious-looking public-area submissions — meaning sites relying solely on that built-in protection remain exposed even if otherwise hardened. No CVSS score was published at initial CERT-FR/vendor disclosure, but subsequent NVD/vulnerability-database entries score it CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) against CPE cpe:2.3:a:spip:spip — network-exploitable, low complexity, no privileges or user interaction required, full compromise of confidentiality, integrity, and availability. EPSS places it at roughly the 90th percentile (~4.2% 30-day exploitation probability), and an independent SSVC assessment rates the exploitation method as "Automatable" with "total" technical impact, consistent with the availability of a scriptable, unauthenticated, single-request exploit. As of this research, CVE-2026-77806 has not yet been added to the CISA Known Exploited Vulnerabilities catalog despite confirmed in-the-wild exploitation.

Remediation is a straightforward version upgrade: SPIP 4.4.21 (or later), delivered via spip_loader 7.0.0 or manual download from get.spip.net. Where immediate patching is not feasible, defenders should block or strip inbound X-Spip-Filtre headers at a WAF or reverse proxy in front of any public-facing SPIP deployment, and monitor forum-submission endpoints for anomalous PHP-filter-name strings, since the vendor's own built-in filtering does not stop this vector.

MITRE ATT&CK techniques by tactic:

Execution

T1059 Command and Scripting Interpreter

Command and Control

T1071 Application Layer Protocol

Initial Access

T1190 Exploit Public-Facing Application

Resource Development

T1588 Obtain Capabilities

Reconnaissance

T1590 Gather Victim Network Information; T1592 Gather Victim Host Information; T1595 Active Scanning

Remediation

Patches

  • SPIP 4.4.21, released 2026-08-20, distributed via spip_loader 7.0.0 or manual download from get.spip.net

Immediate actions

  • Upgrade all internet-facing SPIP instances to 4.4.21 or later immediately
  • If immediate patching is not possible, block or strip any inbound X-Spip-Filtre HTTP header at a WAF or reverse proxy in front of the SPIP instance

Workarounds

  • Filter/strip the X-Spip-Filtre HTTP request header at a WAF, CDN, or reverse proxy for any SPIP site that cannot be patched immediately

Longer-term hardening

  • Do not rely solely on SPIP's built-in security screen (écran de sécurité) for public-facing deployments — this flaw is explicitly not covered by it
  • Monitor forum-preview and other template-rendering endpoints (e.g. ecrire/?exec=forum, forum "texte" field submissions) for requests carrying X-Spip-Filtre headers, PHP filter-name chains, or POST parameters literally named "0"
  • Track SPIP security bulletins and subscribe to CERT-FR advisories for the SPIP product line given the recent two-CVE, two-patch disclosure cadence

Affected and fixed versions

  • SPIP — SPIP CMS
    Vulnerable versions: 4.4.19; 4.4.20; all versions prior to 4.4.21
    Fixed in: 4.4.21

Timeline

  • SPIP releases 4.4.20 as an emergency fix for CVE-2026-77647 (incorrect identification of <?php blocks / var_export mishandling of a leading '<' character), reported anonymously via ANSSI; the Metasploit PR for the related follow-on issue is opened the same day.
  • SPIP project publishes 'Mise a jour critique de securite: sortie de SPIP 4.4.21', confirming the flaw is universal/pre-authentication ('sans conditions'), not mitigated by SPIP's built-in security screen, and that exploitation attempts have already been observed in the wild; users directed to update via spip_loader 7.0.0 or get.spip.net.
  • SPIP 4.4.20 is found to remain vulnerable; SPIP releases 4.4.21 fixing CVE-2026-77806, a second pre-authentication RCE in analyse_resultat_skel() via the X-Spip-Filtre header reachable through the forum-preview "texte" field.
  • CERT-FR publishes advisory CERTFR-2026-AVI-1063, confirming active exploitation of the SPIP flaw.
  • CVE-2026-77806 is reserved and published by MITRE at 13:37:42 UTC.
  • Rapid7 merges the public Metasploit module multi/http/spip_x_spip_filtre_rce (PR #21790, final commit 9809c1e) into metasploit-framework, authored by Julien Voisin (jvoisin) and reviewed by jheysel-r7, bwatters-r7, and Chocapikk; validated against SPIP 4.4.19 and 4.4.20.
  • NVD/OpenCVE last-modify CVE-2026-77806's record, cataloging the CVSS 3.1 9.8 score, CWE-94 classification, EPSS ~4.2% (90th percentile), and an SSVC rating of Automatable exploitation with total technical impact.

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 14 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats