# CVE-2006-7202: Missing authorization in n/a

> Remote attackers can read restricted database content in Mambo CMS due to missing access checks in the PDF generation function.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xxgq-vgj4-4gjj

## What is CVE-2006-7202?

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

### Official description

The dofreePDF function in includes/pdf.php in Mambo 4.6.1 does not properly check access rights for database content, which allows remote attackers to read certain content via unspecified vectors.

## Which versions are affected by CVE-2006-7202?

It affects 1 product.


Products: Mambo Mambo Open Source.

## How do I fix CVE-2006-7202?

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

## Is CVE-2006-7202 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4203](https://insights.sbomify.com/CVE-2007-4203/): Auth bypass in n/a (critical 9.3)
- [CVE-2006-7150](https://insights.sbomify.com/CVE-2006-7150/): SQL injection in n/a (high 7.5)
- [CVE-2004-2072](https://insights.sbomify.com/CVE-2004-2072/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2008-0261](https://insights.sbomify.com/CVE-2008-0261/): Denial of service in n/a (medium 5.0)
- [CVE-2004-1825](https://insights.sbomify.com/CVE-2004-1825/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7202 and fix it if it is affected.

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

## Sources

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

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