# CVE-2006-5381: Information disclosure in n/a

> Remote attackers can obtain database credentials and sensitive information by directly requesting specific database include files in Contenido 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:** 18 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mwh4-fpf8-78h5

## What is CVE-2006-5381?

CVE-2006-5381 is a medium-severity vulnerability in n/a, published on 18 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Contenido CMS stores sensitive data under the web root with insufficient access control, which allows remote attackers to obtain database credentials and other information via a direct request to (1) db_msql.inc, (2) db_mssql.inc, (3) db_mysqli.inc, (4) db_oci8.inc, (5) db_odbc.inc, (6) db_oracle.inc, (7) db_pgsql.inc, or (8) db_sybase.inc in the conlib/ directory.

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

It affects 1 product.


Products: Contenido Contendio.

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

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

## Is CVE-2006-5381 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5380](https://insights.sbomify.com/CVE-2006-5380/): File upload in n/a (high 7.5)
- [CVE-2005-4132](https://insights.sbomify.com/CVE-2005-4132/): Code injection in n/a (high 7.5)
- [CVE-2008-2911](https://insights.sbomify.com/CVE-2008-2911/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2014-9433](https://insights.sbomify.com/CVE-2014-9433/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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