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

> Remote attackers can bypass file upload size restrictions in Mantis by modifying parameters, allowing unauthorized large file uploads.

- **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:** Yes
- **Published:** 28 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-722p-jr5h-rjqr

## What is CVE-2005-4518?

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

### Official description

Mantis before 0.19.4 allows remote attackers to bypass the file upload size restriction by modifying the max_file_size parameter to (1) bug_file_add.php, (2) bug_report.php, (3) bug_report_advanced_page.php, and (4) proj_doc_add_page.php.

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


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

Upgrade to a fixed version.

## Is CVE-2005-4518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4518 is a high-severity vulnerability in n/a, published on 28 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4518 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-4518/ (Markdown: https://insights.sbomify.com/CVE-2005-4518/index.md)
```

## Sources

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

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