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

> Remote attackers can gain administrative privileges by directly accessing useradded.php with a modified username, bypassing authentication controls.

- **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:** 18 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qpvv-7mvp-82fr

## What is CVE-2008-2294?

CVE-2008-2294 is a high-severity missing authorization vulnerability in n/a, published on 18 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pet Grooming Management System 2.0 allows remote attackers to gain privileges via a direct request to useradded.php with a modified user name for "admin."

Weakness: CWE-264

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

It affects 1 product.


Products: Mreaves Pet Grooming Management System.

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

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

## Is CVE-2008-2294 being exploited?

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

Public exploit code:

- Pet Grooming Management System 2.0 - Arbitrary Add Admin (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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