# CVE-2007-1639: File upload in n/a

> Authenticated users can upload and execute arbitrary PHP code in PHProjekt when magic_quotes_gpc is disabled, leading to remote code execution.

- **Severity:** Medium 4.6 (`AV:N/AC:H/Au:S/C:P/I:P/A:P`)
- **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:** 23 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v5j6-x93w-hw46

## What is CVE-2007-1639?

CVE-2007-1639 is a medium-severity vulnerability in n/a, published on 23 Mar 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in PHProjekt 5.2.0, when magic_quotes_gpc is disabled, allows remote authenticated users to upload and execute arbitrary PHP code via a file with an executable extension, which is then accessed by the (1) calendar or (2) file management module, or possibly unspecified other files.

## Which versions are affected by CVE-2007-1639?

It affects 1 product.


Products: Phpprojekt Phpprojekt.

## How do I fix CVE-2007-1639?

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

## Is CVE-2007-1639 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0451](https://insights.sbomify.com/CVE-2002-0451/): Code injection in n/a (high 7.5)
- [CVE-2001-0995](https://insights.sbomify.com/CVE-2001-0995/): Missing authorization in n/a (high 7.5)
- [CVE-2007-1638](https://insights.sbomify.com/CVE-2007-1638/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2006-4609](https://insights.sbomify.com/CVE-2006-4609/): File upload in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1639 and fix it if it is affected.

What it is: CVE-2007-1639 is a medium-severity vulnerability in n/a, published on 23 Mar 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-1639 in the wild and no public exploit code.

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

## Sources

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

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