# CVE-2008-0246: Missing authorization in n/a

> Remote attackers can gain administrator privileges by changing the password without providing the original one in UploadScript.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 12 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6234-8gq6-2wgj

## What is CVE-2008-0246?

CVE-2008-0246 is a critical missing authorization vulnerability in n/a, published on 12 Jan 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

admin.php in UploadScript 1.0 does not check for the original password before making a change to a new password, which allows remote attackers to gain administrator privileges via the pass parameter in a nopass (Set Password) action.

Weakness: CWE-264

## Which versions are affected by CVE-2008-0246?

It affects 2 products.


Products: Uploadscript Uploadimage, Uploadscript Uploadscript.

## How do I fix CVE-2008-0246?

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

## Is CVE-2008-0246 being exploited?

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

Public exploit code:

- UploadImage/UploadScript 1.0 - Remote Change Admin Password (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-0245](https://insights.sbomify.com/CVE-2008-0245/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0246 and fix it if it is affected.

What it is: CVE-2008-0246 is a critical missing authorization vulnerability in n/a, published on 12 Jan 2008. 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-2008-0246 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-2008-0246/ (Markdown: https://insights.sbomify.com/CVE-2008-0246/index.md)
```

## Sources

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

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