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

> Remote attackers can access sensitive database credentials by directly requesting the accms.dat file due to insufficient access controls.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xm36-9rp9-846v

## What is CVE-2008-7069?

CVE-2008-7069 is a high-severity vulnerability in n/a, published on 25 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All Club CMS (ACCMS) 0.0.2 and earlier stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain database configuration information, including credentials, via a direct request to accms.dat.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Paul Arbogast Accms.

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

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

## Is CVE-2008-7069 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-7069 exists.

Public exploit code:

- All Club CMS 0.0.2 - Remote Database Configuration Retrieve (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7069 is a high-severity vulnerability in n/a, published on 25 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-7069 exists.

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-7069/ (Markdown: https://insights.sbomify.com/CVE-2008-7069/index.md)
```

## Sources

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

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