SPIP before 4.3.2, 4.2.16, and 4.1.18 is vulnerable to a command injection issue.
CVE-2024-8517 · GHSA-7w4r-xxr6-xrcj · EUVD-2024-49235 · published 6 Sept 2024
How serious is it
- Severity: critical, CVSS score 9.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2024-8517?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- SPIP SPIP: 4.2.0 ≤4.2.15
- SPIP SPIP: 4.1.0 <4.1.18
- SPIP SPIP: 4.3.0 ≤4.3.1
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
SPIP before 4.3.2, 4.2.16, and
4.1.18 is vulnerable to a command injection issue. A
remote and unauthenticated attacker can execute arbitrary operating system commands by sending a crafted multipart file upload HTTP request.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- thinkloveshare.com/hacking/spip_preauth_rce_2024_part_2_a_big_upload/
- blog.spip.net/Mise-a-jour-critique-de-securite-sortie-de-SPIP-4-3-2-SPIP-4-2-16-SPIP-4-1-18.html
- vulncheck.com/advisories/spip-upload-rce
- vozec.fr/researchs/spip-preauth-rce-2024-big-upload/
Merged from ENISA EUVD. Last updated 30 Oct 2026. All vulnerabilities · RSS · JSON