# CVE-2003-0482: File upload in n/a

> Remote attackers can execute arbitrary code by uploading malicious files via file_new.php and accessing them directly.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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:** 28 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hhh4-2vgc-rxh8

## What is CVE-2003-0482?

CVE-2003-0482 is a high-severity vulnerability in n/a, published on 28 Jun 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TUTOS 1.1 allows remote attackers to execute arbitrary code by uploading the code using file_new.php, then directly accessing the uploaded code via a request to the repository containing the code.

## Which versions are affected by CVE-2003-0482?

It affects 1 product.


Products: Gero Kohnert Tutos.

## How do I fix CVE-2003-0482?

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

## Is CVE-2003-0482 being exploited?

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

Public exploit code:

- Tutos 1.1 - File_New Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-0481](https://insights.sbomify.com/CVE-2003-0481/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0482 and fix it if it is affected.

What it is: CVE-2003-0482 is a high-severity vulnerability in n/a, published on 28 Jun 2003. 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-2003-0482 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-2003-0482/ (Markdown: https://insights.sbomify.com/CVE-2003-0482/index.md)
```

## Sources

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

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