# CVE-2024-8517: SPIP Bigup Multipart File Upload OS Command Injection

> Remote unauthenticated attackers can execute arbitrary OS commands via crafted multipart file uploads in SPIP CMS.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Sep 2024
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2024-8517, GHSA-7w4r-xxr6-xrcj, UBUNTU-CVE-2024-8517

## What is CVE-2024-8517?

CVE-2024-8517 is a critical command injection vulnerability in Spip Spip, published on 6 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2024-8517?

It affects 1 product.


Products: Spip Spip.

## How do I fix CVE-2024-8517?

Upgrade to a fixed version.

## Is CVE-2024-8517 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8517 exists.

Public exploit code:

- SPIP BigUp Plugin Unauthenticated RCE (github_poc): https://github.com/Chocapikk/CVE-2024-8517
- This Python exploit targets a critical unauthenticated Remote Code Execution (RCE) vulnerability in the BigUp plugin of SPIP CMS (≤ 4.3.1, 4.2.15, 4.1.17). It abuses the bigup_retrouver_fichiers parameter, allowing attackers to execute arbitrary PHP via upload progress features, without authentication. (github_poc): https://github.com/saadhassan77/SPIP-BigUp-Unauthenticated-RCE-Exploit-CVE-2024-8517
- SPIP BigUp Plugin Unauthenticated RCE (metasploit)
- SPIP BigUp Plugin - Remote Code Execution (nuclei): http/cves/2024/CVE-2024-8517.yaml

## Other vulnerabilities in Spip Spip

- [CVE-2012-4331](https://insights.sbomify.com/CVE-2012-4331/): Other in n/a (critical 10.0)
- [CVE-2008-5812](https://insights.sbomify.com/CVE-2008-5812/): Other in n/a (critical 10.0)
- [CVE-2023-24258](https://insights.sbomify.com/CVE-2023-24258/): SQL injection in n/a (critical 9.8)
- [CVE-2017-9736](https://insights.sbomify.com/CVE-2017-9736/): Command injection in n/a (critical 9.8)
- [CVE-2016-3154](https://insights.sbomify.com/CVE-2016-3154/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8517 and fix it if it is affected.

What it is: CVE-2024-8517 is a critical command injection vulnerability in Spip Spip, published on 6 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8517 exists.

Affected product: Spip Spip. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8517/ (Markdown: https://insights.sbomify.com/CVE-2024-8517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8517
- OSV: https://osv.dev/vulnerability/CVE-2024-8517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8517/
Summaries are generated and may contain mistakes; the official description above is the record.