Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2025-71243: Unauthenticated RCE in SPIP Saisies plugin via _anciennes_valeurs PHP code injection

Published Feb 19, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v4
EPSS5.5%93rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Spip
IdentifiersCVE-2025-71243CWE-94 · Improper Control of Generation of…

CVE-2025-71243 is a critical unauthenticated remote code execution vulnerability in the SPIP plugin 'Saisies pour formulaire' (Saisies) affecting versions 5.4.0 through 5.11.0. The flaw is caused by unsafe handling of the user-controlled _anciennes_valeurs form parameter in the plugin’s form-loading path. According to the provided content, saisies_formulaire_charger_generer_hidden_ancienne_valeur_depubliee() can assign attacker-supplied _anciennes_valeurs directly to $encode without sanitization, and the value is then appended into $flux['data']['_hidden'] via the formulaire_charger pipeline. In SPIP, underscore-prefixed fields bypass protege_champ() escaping, and the #ACTION_FORMULAIRE balise renders _hidden content with interdire_scripts=false, disabling normal script filtering. Because SPIP templates are compiled into PHP and executed via eval(), injected <?php ... ?> sequences can survive rendering and execute server-side. The issue is reachable during the form 'charger' phase, so exploitation does not require successful form submission. The content states exploitation is possible with a simple unauthenticated GET or POST request containing _anciennes_valeurs, provided a publicly accessible form using the Saisies plugin is present.

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 provides arbitrary server-side PHP code execution in the context of the web server/SPIP process. This can enable full application compromise, execution of system commands, theft or modification of site data, deployment of web shells or other persistence mechanisms, lateral movement from the compromised host, and complete compromise of confidentiality, integrity, and availability. The supplied CVSS vectors and advisory context indicate no privileges or user interaction are required.

Mitigation

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

Primary mitigation is to patch immediately to Saisies 5.11.1+. If immediate patching is not possible, reduce exposure by restricting public access to pages containing Saisies-powered forms, especially forms exposed through plugins such as Formidable. Additional hardening noted in the content includes disabling dangerous PHP functions such as system, exec, passthru, shell_exec, and proc_open to reduce post-exploitation impact, though this does not remove the underlying vulnerability.

Remediation

Patch, then assume compromise.

Upgrade the SPIP 'Saisies pour formulaire' (Saisies) plugin to version 5.11.1 or later. The provided content states the fix removes the branch that trusted user-supplied _anciennes_valeurs and instead forces server-side recomputation of the value, eliminating the attacker-controlled code injection path. Confirm that all affected instances running versions 5.4.0 through 5.11.0 are updated.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2025-71243Repository purpose: provides an unauthenticated RCE exploit (CVE-2025-71243) for the SPIP ‘Saisies’ plugin, plus a Docker-based lab to reproduce the issue. Key vulnerability mechanics (as described and implemented): the Saisies pipeline function that generates a hidden field trusts the POST parameter `_anciennes_valeurs` and interpolates it into a single-quoted HTML attribute without escaping. SPIP’s `#ACTION_FORMULAIRE` rendering sets `interdire_scripts=false` for the `_hidden` field, and the template is evaluated, allowing injected `<?php ... ?>` to execute. This yields unauthenticated PHP code execution on any public page containing a saisies-powered form. Exploit capabilities (exploit.py): - Version fingerprinting: requests `/<origin>/spip.php` and parses the `Composed-By` header for `saisies(x.y.z)`; optionally fetches `/<origin>/local/config.txt` (or a config.txt URL embedded in the header) to extract the plugin version. - Optional site discovery: `--crawl` starts from `/<origin>/spip.php?page=plan` (SPIP plan/sitemap) and follows internal links (filters common static assets) until it finds a page whose HTML contains the parameter name `_anciennes_valeurs`, indicating a saisies form. - Vulnerability check: POSTs `_anciennes_valeurs` with an injected PHP `echo` marker and checks for marker presence in the response. - RCE: base64-encodes an operator-supplied command and injects PHP `system(base64_decode(...))`; extracts command output from between two known HTML markers in the response. - Interactive mode: provides a simple read-eval loop that repeatedly sends commands and prints extracted output. Repository structure: - README.md: detailed write-up, affected versions (5.4.0–5.11.0, fixed 5.11.1), exploitation example, and usage instructions. - exploit.py: standalone Python3 exploit using `requests` and basic HTML parsing. - lab/docker-compose.yml: spins up `spip:4.3-apache` plus `mariadb:10`, exposing SPIP on port 8888. - lab/setup.sh: provisions a vulnerable environment by downloading Saisies v5.11.0, activating it via DB meta update, and creating a public contact form/page that uses saisies so the exploit can be tested end-to-end.Chocapikk · Disclosed Feb 19, 2026 · python · bash · networkOperational
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
SpipSaisiesapplication
SpipSaisies Pour Formulaireapplication
FAQ

Frequently asked questions

Is CVE-2025-71243 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-71243 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-71243?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-71243, the earliest disclosed Feb 19, 2026.
Is there a patch for CVE-2025-71243?
Upgrade the SPIP 'Saisies pour formulaire' (Saisies) plugin to version 5.11.1 or later. The provided content states the fix removes the branch that trusted user-supplied _anciennes_valeurs and instead forces server-side recomputation of the value, eliminating the attacker-controlled code injection path.
What products are affected by CVE-2025-71243?
Spip Saisies and Spip Saisies Pour Formulaire.
How severe is CVE-2025-71243?
CVE-2025-71243 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 5.5% (93rd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity11Community discussion across Reddit, Mastodon, and other social sources.