Is CVE-2026-8429 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-8429 being exploited in the wild.

How severe is CVE-2026-8429?

High severity, with a CVSS score of 8.8, published 12 May 2026.

Is there a fix for CVE-2026-8429?

A patch was published on 2026-05-12: Released in SPIP 4.4.14 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-8429 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-8429?

Check whether you run Spip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-8429: SPIP remote code execution in private space

CVE-2026-8429 · Severity: high · CVSS 8.8 · Published 2026-05-12

SPIP is a popular open-source content management system used to publish and manage websites. A security vulnerability in the software's administrative interface (the 'private space') allows an attacker with low-level access to execute malicious code on the server. This could lead to a complete takeover of the website, theft of sensitive data, or disruption of services, even if standard security screens are active.

Technologies: Spip. Vendors: Spip.

Quick answers

Is CVE-2026-8429 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8429 being exploited in the wild.
How severe is CVE-2026-8429?: High severity, with a CVSS score of 8.8, published 12 May 2026.
Which products and versions are affected?: Spip < 4.4.14.
Is there a fix for CVE-2026-8429?: A patch was published on 2026-05-12: Released in SPIP 4.4.14 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-8429 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-8429?: Check whether you run Spip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A remote code execution (RCE) vulnerability exists in SPIP versions prior to 4.4.14 within the 'private space' (administrative area). The flaw is classified as CWE-94 (Improper Control of Generation of Code) and allows an attacker with low-privileged (PR:L) access to execute arbitrary PHP code in the context of the web server. Notably, the exploit bypasses the 'SPIP security screen' (écran de sécurité), a common hardening measure for the platform. The vulnerability is addressed in version 4.4.14. A separate RCE vulnerability affecting the public space in specific Nginx configurations was also patched in the same release, but this specific entry (CVE-2026-8429) focuses on the private space flaw.

Affected products

SPIP SPIP < 4.4.14

Timeline

2026-05-12: disclosed
2026-05-12: patched: Released in SPIP 4.4.14
2026-05-12: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.