# CVE-2007-0546: Information disclosure in n/a

> Remote attackers can download the database containing passwords by directly requesting db.mdb due to insufficient access control.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/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:** 29 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j44m-42w4-86q9

## What is CVE-2007-0546?

CVE-2007-0546 is a high-severity vulnerability in n/a, published on 29 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Toxiclab Shoutbox 1 stores sensitive information under the web root with insufficient access control, which allows remote attackers to download a database containing passwords via a direct request for db.mdb.

## Which versions are affected by CVE-2007-0546?

It affects 1 product.


Products: Toxiclab Shoutbox.

## How do I fix CVE-2007-0546?

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

## Is CVE-2007-0546 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0546 and fix it if it is affected.

What it is: CVE-2007-0546 is a high-severity vulnerability in n/a, published on 29 Jan 2007. 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-2007-0546 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-2007-0546/ (Markdown: https://insights.sbomify.com/CVE-2007-0546/index.md)
```

## Sources

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

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