# CVE-2013-2562: Information disclosure in n/a

> Local attackers can read the MySQL database password stored in cleartext within the Mambo CMS document root, leading to sensitive information disclosure.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-chqj-hwq4-xccf

## What is CVE-2013-2562?

CVE-2013-2562 is a low-severity vulnerability in n/a, published on 9 Jun 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Mambo CMS 4.6.5 stores the MySQL database password in cleartext in the document root, which allows local users to obtain sensitive information via unspecified vectors.

Weakness: CWE-255

## Which versions are affected by CVE-2013-2562?

It affects 1 product.


Products: Mambo-Foundation Mambo Cms.

## How do I fix CVE-2013-2562?

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

## Is CVE-2013-2562 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2499](https://insights.sbomify.com/CVE-2011-2499/): Cross-site scripting in CMS (medium 6.1)
- [CVE-2013-2565](https://insights.sbomify.com/CVE-2013-2565/): Information disclosure in Mambo CMS (medium 5.3)
- [CVE-2013-2564](https://insights.sbomify.com/CVE-2013-2564/): Denial of service in n/a (medium 5.0)
- [CVE-2013-2563](https://insights.sbomify.com/CVE-2013-2563/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2562 and fix it if it is affected.

What it is: CVE-2013-2562 is a low-severity vulnerability in n/a, published on 9 Jun 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2562 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-2013-2562/ (Markdown: https://insights.sbomify.com/CVE-2013-2562/index.md)
```

## Sources

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

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