# CVE-2005-4007: Missing authorization in n/a

> Unspecified authorization flaws in SAPID CMS allow newly registered users to bypass security checks, potentially leading to privilege escalation.

- **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:** 5 Dec 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rq6v-h9fq-jw26

## What is CVE-2005-4007?

CVE-2005-4007 is a critical missing authorization vulnerability in n/a, published on 5 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple unspecified vulnerabilities in SAPID CMS before 1.2.3.03, related to newly registered users and possibly authorization checks, have unknown impact and attack vectors involving (1) mvc/controller/user_request_analysis.inc.php and (2) usr/xml/ddc/authorization.xml.

## Which versions are affected by CVE-2005-4007?

It affects 1 product.


Products: Redgraphic Sapid Cms.

## How do I fix CVE-2005-4007?

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

## Is CVE-2005-4007 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5293](https://insights.sbomify.com/CVE-2012-5293/): Code injection in n/a (high 7.5)
- [CVE-2006-4026](https://insights.sbomify.com/CVE-2006-4026/): Code injection in n/a (high 7.5)
- [CVE-2005-4006](https://insights.sbomify.com/CVE-2005-4006/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4007 and fix it if it is affected.

What it is: CVE-2005-4007 is a critical missing authorization vulnerability in n/a, published on 5 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4007 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-2005-4007/ (Markdown: https://insights.sbomify.com/CVE-2005-4007/index.md)
```

## Sources

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

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