# CVE-2026-8430: SPIP remote code execution in public space via Nginx

Source: https://junglewise.ai/threats/cve-2026-8430-spip-remote-code-execution-in-public-space-via-nginx  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-12. Updated: 2026-05-14  
License: CC BY 4.0 with a link back

CVE-2026-8430 · Severity: high · CVSS 8.1 · Published 2026-05-12

SPIP is a popular open-source content management system (CMS) used to build and manage websites. A security vulnerability in versions prior to 4.4.14 allows remote attackers to execute malicious code on the web server under specific Nginx configurations. This could lead to a complete takeover of the website, unauthorized access to sensitive data, or disruption of services.

Technologies: [Spip](https://junglewise.ai/threats/technologies/spip). Vendors: [Spip](https://junglewise.ai/threats/vendors/spip).

## Quick answers

**Is CVE-2026-8430 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-8430 being exploited in the wild.

**How severe is CVE-2026-8430?** High severity, with a CVSS score of 8.1, published 12 May 2026.

**Which products and versions are affected?** Spip < 4.4.14.

**Is there a fix for CVE-2026-8430?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-8430 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-8430?** 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 the public space of SPIP versions prior to 4.4.14. The flaw is classified as CWE-94 (Improper Control of Generation of Code) and is triggered under specific Nginx configuration scenarios that interact poorly with SPIP's routing or processing. An unauthenticated remote attacker can exploit this to execute arbitrary PHP code in the context of the web server. Notably, the 'SPIP security screen' (ecran de securite) does not provide protection against this specific flaw. The issue is resolved in SPIP version 4.4.14.

## Affected products

- SPIP SPIP < 4.4.14

## Timeline

- 2026-05-12: disclosed: Vulnerability disclosed and patched in version 4.4.14
- 2026-05-12: advisory: NVD published the CVE record

## References

- [https://blog.spip.net/](https://blog.spip.net/)
- [https://www.vulncheck.com/advisories/spip-prior-to-remote-code-execution-via-nginx](https://www.vulncheck.com/advisories/spip-prior-to-remote-code-execution-via-nginx)

## Related threats

- [SPIP SQL injection via parameter mismatch](https://junglewise.ai/threats/cve-2026-122032-spip-before-4-4-29-contains-a-sql-injection-vulnerability-that)
- [SPIP server-side request forgery in recuperer_url()](https://junglewise.ai/threats/cve-2026-109378-spip-before-4-4-18-contains-a-server-side-request-forgery)
- [SPIP mass assignment in editer_objet leading to RCE](https://junglewise.ai/threats/cve-2026-72710-spip-mass-assignment-in-editer-objet-leading-to-rce)
- [SPIP missing authorization in sensitive actions](https://junglewise.ai/threats/cve-2026-72709-spip-missing-authorization-in-sensitive-actions)
- [SPIP unauthenticated blind SQL injection in SQL escaping](https://junglewise.ai/threats/cve-2026-72708-spip-unauthenticated-blind-sql-injection-in-sql-escaping)