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

> Remote attackers can obtain sensitive path information and directory listings by directly requesting specific PHP files and directories in AngelineCMS.

- **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:** 12 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c7jx-9p8f-4pcm

## What is CVE-2006-2329?

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

### Official description

AngelineCMS 0.6.5 and earlier allow remote attackers to obtain sensitive information via a direct request for (1) adodb-access.inc.php, (2) adodb-ado.inc.php, (3) adodb-ado_access.inc, (4) adodb-ado_mssql.inc.php, (5) adodb-borland_ibase, (6) adodb-csv.inc.php, (7) adodb-db2.inc.php, (8) adodb-fbsql.inc.php, (9) adodb-firebird.inc.php, (10) adodb-ibase.inc.php, (11) adodb-informix.inc.php, (12) adodb-informix72.inc, (13) adodb-mssql.inc.php, (14) adodb-mssqlpo.inc.php, (15) adodb-mysql.inc.php, (16) adodb-mysqlt.inc.php, (17) adodb-oci8.inc.php, (18) adodb-oci805.inc.php, (19) adodb-oci8po.inc.php, and (20) adodb-odbc.inc.php, which reveal the path in various error messages; and via a direct request for the (21) lib/system/ directory and (22) possibly other lib/ directories, which provide a directory listing and "architecture view."

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

It affects 1 product.


Products: Angelinecms Angelinecms.

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

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

## Is CVE-2006-2329 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1653](https://insights.sbomify.com/CVE-2006-1653/): Code injection in n/a (high 7.5)
- [CVE-2006-2328](https://insights.sbomify.com/CVE-2006-2328/): SQL injection in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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