# CVE-2005-2699: File upload in n/a

> Authenticated administrators can upload malicious PHP files to execute arbitrary code, though this may not cross privilege boundaries if admin access is already required.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h455-x6w8-x79r

## What is CVE-2005-2699?

CVE-2005-2699 is a medium-severity vulnerability in n/a, published on 25 Aug 2005. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted file upload vulnerability in admin/admin.php in PHPKit 1.6.1 allows remote authenticated administrators to execute arbitrary PHP code by uploading a .php file to the content/images/ directory using images.php.  NOTE: if a PHPKit administrator must already have access to the end system to install or modify configuration of the product, then this issue might not cross privilege boundaries, and should not be included in CVE.

## Which versions are affected by CVE-2005-2699?

It affects 1 product.


Products: Phpkit Phpkit.

## How do I fix CVE-2005-2699?

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

## Is CVE-2005-2699 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10758](https://insights.sbomify.com/CVE-2016-10758/): File upload in n/a (high 8.8)
- [CVE-2007-6134](https://insights.sbomify.com/CVE-2007-6134/): SQL injection in n/a (high 7.5)
- [CVE-2006-7115](https://insights.sbomify.com/CVE-2006-7115/): SQL injection in n/a (high 7.5)
- [CVE-2007-0179](https://insights.sbomify.com/CVE-2007-0179/): SQL injection in n/a (high 7.5)
- [CVE-2005-3553](https://insights.sbomify.com/CVE-2005-3553/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2699 and fix it if it is affected.

What it is: CVE-2005-2699 is a medium-severity vulnerability in n/a, published on 25 Aug 2005. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2699 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-2005-2699/ (Markdown: https://insights.sbomify.com/CVE-2005-2699/index.md)
```

## Sources

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

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