# CVE-2005-0854: Missing authorization in n/a

> Remote attackers can bypass authentication to upload or delete files in bp blog by directly accessing specific ASP scripts.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gxx9-qh4p-rcv4

## What is CVE-2005-0854?

CVE-2005-0854 is a high-severity missing authorization vulnerability in n/a, published on 24 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

betaparticle blog (bp blog), posisbly before version 4, allows remote attackers to bypass authentication and (1) upload files via a direct request to upload.asp or (2) delete files via a direct request to myFiles.asp.

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

It affects 1 product.


Products: Betaparticle Betaparticle Blog.

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

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

## Is CVE-2005-0854 being exploited?

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

Public exploit code:

- BetaParticle blog 2.0/3.0 - 'upload.asp' Arbitrary File Upload (exploitdb)
- BetaParticle blog 2.0/3.0 - 'myFiles.asp' File Manipulation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-1445](https://insights.sbomify.com/CVE-2007-1445/): SQL injection in n/a (high 7.5)
- [CVE-2006-1333](https://insights.sbomify.com/CVE-2006-1333/): SQL injection in n/a (medium 6.4)
- [CVE-2005-0853](https://insights.sbomify.com/CVE-2005-0853/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0854 is a high-severity missing authorization vulnerability in n/a, published on 24 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0854 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-2005-0854/ (Markdown: https://insights.sbomify.com/CVE-2005-0854/index.md)
```

## Sources

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

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