# CVE-2021-44123: File upload in n/a

> Attackers can execute arbitrary code by uploading and clicking a malicious image with a double extension in SPIP.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-44123, GHSA-6f8p-g935-8f29, UBUNTU-CVE-2021-44123

## What is CVE-2021-44123?

CVE-2021-44123 is a high-severity vulnerability in Spip Spip, published on 26 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SPIP 4.0.0 is affected by a remote command execution vulnerability. To exploit the vulnerability, an attacker must craft a malicious picture with a double extension, upload it and then click on it to execute it.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2021-44123?

It affects 1 product.


Products: Spip Spip.

## How do I fix CVE-2021-44123?

Upgrade to a fixed version.

## Is CVE-2021-44123 being exploited?

There is no known exploitation of CVE-2021-44123 in the wild and no public exploit code.

## 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-2024-8517](https://insights.sbomify.com/CVE-2024-8517/): SPIP Bigup Multipart File Upload OS Command Injection (critical 9.8)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-44123 and fix it if it is affected.

What it is: CVE-2021-44123 is a high-severity vulnerability in Spip Spip, published on 26 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-44123 in the wild and no public exploit code.

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-2021-44123/ (Markdown: https://insights.sbomify.com/CVE-2021-44123/index.md)
```

## Sources

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

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