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

> Remote attackers can execute arbitrary code by uploading malicious files due to insufficient file type restrictions in BoastMachine.

- **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:** 14 May 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-p63p-f4jm-qw85

## What is CVE-2005-1580?

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

### Official description

users.ini.php in BoastMachine 3.0 does not properly restrict the types of files that can be uploaded, which allows remote attackers to execute arbitrary code.

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

It affects 1 product.


Products: Boastmachine Boastmachine.

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

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

## Is CVE-2005-1580 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-0422](https://insights.sbomify.com/CVE-2008-0422/): SQL injection in n/a (high 7.5)
- [CVE-2006-2491](https://insights.sbomify.com/CVE-2006-2491/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2007-2860](https://insights.sbomify.com/CVE-2007-2860/): Privilege escalation in n/a (medium 6.5)
- [CVE-2007-5417](https://insights.sbomify.com/CVE-2007-5417/): Path traversal in n/a (medium 5.0)
- [CVE-2006-0131](https://insights.sbomify.com/CVE-2006-0131/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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