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

> Authenticated users can change arbitrary passwords via modified uid parameter, enabling account takeover and privilege escalation.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/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:** 25 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jjjm-vgrm-72p6

## What is CVE-2008-6524?

CVE-2008-6524 is a medium-severity missing authorization vulnerability in n/a, published on 25 Mar 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

resetpass.php in openInvoice 0.90 beta and earlier allows remote authenticated users to change the passwords of arbitrary users via a modified uid parameter.  NOTE: this can be leveraged with a separate vulnerability in auth.php to modify passwords without authentication.

Weakness: CWE-255

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

It affects 1 product.


Products: Cale Dunlap Openinvoice.

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

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

## Is CVE-2008-6524 being exploited?

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

Public exploit code:

- OpenInvoice 0.9 - Arbitrary Change User Password (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6524 is a medium-severity missing authorization vulnerability in n/a, published on 25 Mar 2009. 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-6524 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-6524/ (Markdown: https://insights.sbomify.com/CVE-2008-6524/index.md)
```

## Sources

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

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