# CVE-2024-29272: VvvebJs Arbitrary File Upload vulnerability

> Unauthenticated attackers can upload arbitrary files via save.php to execute code and read sensitive data in VvvebJs.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-pmm3-68q9-57jg

## What is CVE-2024-29272?

CVE-2024-29272 is a medium-severity vulnerability in n/a, published on 22 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arbitrary File Upload vulnerability in VvvebJs before version 1.7.5, allows unauthenticated remote attackers to execute arbitrary code and obtain sensitive information via the sanitizeFileName parameter in save.php.

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

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

2 open source packages ship an affected version, including vvvebJs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vvvebJs` | npm | All versions | 1.7.5 |
| `vvvebJs` | npm | All versions | 1.7.5 |

Products: Vvveb Vvvebjs.

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

Upgrade vvvebJs to 1.7.5 or later.

## Is CVE-2024-29272 being exploited?

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

Public exploit code:

- https://github.com/awjkjflkwlekfdjs/CVE-2024-29272 (github_poc): https://github.com/awjkjflkwlekfdjs/CVE-2024-29272
- VvvebJs < 1.7.5 - Arbitrary File Upload (nuclei): http/cves/2024/CVE-2024-29272.yaml

## Other vulnerabilities in n/a

- [CVE-2024-25182](https://insights.sbomify.com/CVE-2024-25182/): File upload in n/a (critical 9.8)
- [CVE-2024-27480](https://insights.sbomify.com/CVE-2024-27480/): File upload in n/a (critical 9.8)
- [CVE-2024-25181](https://insights.sbomify.com/CVE-2024-25181/): Server-side request forgery in n/a (critical 9.1)
- [CVE-2024-25183](https://insights.sbomify.com/CVE-2024-25183/): Path traversal in n/a (high 7.5)
- [CVE-2024-29271](https://insights.sbomify.com/CVE-2024-29271/): VvvebJs Reflected Cross-Site Scripting (XSS) vulnerability (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29272 is a medium-severity vulnerability in n/a, published on 22 Mar 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-29272 exists.

Affected packages and fixed versions:
- vvvebJs (npm): affected all versions; fixed in 1.7.5
- vvvebJs (npm): affected all versions; fixed in 1.7.5

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

## Sources

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

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