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

> Authenticated users can access the admin panel without proper authorization, allowing them to modify user privileges and delete accounts.

- **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 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gw6p-34jh-g7qg

## What is CVE-2008-4245?

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

### Official description

The Admin Control Panel in Rianxosencabos CMS 0.9 does not require administrator privileges, which allows remote authenticated users to (1) change a user's privileges, (2) delete a user account, or perform unspecified other administrative actions via vectors involving an admin lista action to the default URI, possibly related to useradmin.php.

Weakness: CWE-264

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

It affects 1 product.


Products: Rianxosencabos Cms Rianxosencabos Cms.

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

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

## Is CVE-2008-4245 being exploited?

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

Public exploit code:

- Rianxosencabos CMS 0.9 - Arbitrary Add Admin (exploitdb)

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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