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

> Remote attackers can upload arbitrary files to MauryCMS without authentication due to missing authorization checks in the file manager.

- **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:** 12 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r76h-m46c-jfwg

## What is CVE-2008-6951?

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

### Official description

MauryCMS 0.53.2 and earlier does not require administrative authentication for Editors/fckeditor/editor/filemanager/browser/default/browser.html, which allows remote attackers to upload arbitrary files via a direct request.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Cms.maury91 Maurycms.

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

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

## Is CVE-2008-6951 being exploited?

There is no known exploitation of CVE-2008-6951 in the wild and no public exploit code.

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6951 is a high-severity missing authorization vulnerability in n/a, published on 12 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-6951 in the wild and no public exploit code.

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-6951/ (Markdown: https://insights.sbomify.com/CVE-2008-6951/index.md)
```

## Sources

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

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