# CVE-2024-29387: File upload in n/a

> Attackers can achieve remote code execution in ProjectQtor via a file upload vulnerability in the print component.

- **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:** No
- **Published:** 4 Apr 2024
- **Updated:** 16 Aug 2024
- **Also known as:** GHSA-4x7j-vfwq-rj38

## What is CVE-2024-29387?

CVE-2024-29387 is a high-severity vulnerability in n/a, published on 4 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

projeqtor up to 11.2.0 was discovered to contain a remote code execution (RCE) vulnerability via the component /view/print.php.

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

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

It affects 1 product.


Products: Projeqtor Projeqtor.

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

No fix has been published for CVE-2024-29387 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-29387 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-42940](https://insights.sbomify.com/CVE-2021-42940/): Cross-site scripting in n/a (critical 9.9)
- [CVE-2018-18924](https://insights.sbomify.com/CVE-2018-18924/): File upload in n/a (high 8.8)
- [CVE-2017-11760](https://insights.sbomify.com/CVE-2017-11760/): File upload in n/a (high 8.8)
- [CVE-2013-6164](https://insights.sbomify.com/CVE-2013-6164/): SQL injection in n/a (high 7.5)
- [CVE-2023-49034](https://insights.sbomify.com/CVE-2023-49034/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29387 is a high-severity vulnerability in n/a, published on 4 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29387 exists.

Affected product: n/a. 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-29387/ (Markdown: https://insights.sbomify.com/CVE-2024-29387/index.md)
```

## Sources

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

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