# CVE-2008-7212: Information disclosure in n/a

> Remote attackers can obtain sensitive installation path information via error messages in the MOStlyCE plugin for Mambo CMS.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 11 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3mg9-wjxc-5593

## What is CVE-2008-7212?

CVE-2008-7212 is a medium-severity vulnerability in n/a, published on 11 Sep 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MOStlyCE before 2.4, as used in Mambo 4.6.3 and earlier, allows remote attackers to obtain sensitive information via certain requests to mambots/editors/mostlyce/jscripts/tiny_mce/filemanager/connectors/php/connector.php, which reveals the installation path in an error message.

Weakness: CWE-264

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

It affects 2 products.


Products: Brilaps Mostlyce, Mambo-Foundation Mambo.

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

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

## Is CVE-2008-7212 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7214](https://insights.sbomify.com/CVE-2008-7214/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2008-7215](https://insights.sbomify.com/CVE-2008-7215/): File upload in n/a (medium 5.8)
- [CVE-2008-7213](https://insights.sbomify.com/CVE-2008-7213/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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