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

> Remote attackers can obtain the database password by triggering connection errors in Quicksilver Forums, exposing sensitive credentials.

- **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:** 1 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g9rq-g8g7-67pr

## What is CVE-2007-5172?

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

### Official description

Quicksilver Forums before 1.4.1 allows remote attackers to obtain sensitive information by causing unspecified connection errors, which reveals the database password in the resulting error message.

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

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

It affects 1 product.


Products: Quicksilver Forums Quicksilver Forums.

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

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

## Is CVE-2007-5172 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-7064](https://insights.sbomify.com/CVE-2008-7064/): Path traversal in n/a (high 7.5)
- [CVE-2008-3601](https://insights.sbomify.com/CVE-2008-3601/): SQL injection in n/a (high 7.5)
- [CVE-2006-4824](https://insights.sbomify.com/CVE-2006-4824/): Code injection in n/a (high 7.5)
- [CVE-2005-4030](https://insights.sbomify.com/CVE-2005-4030/): SQL injection in n/a (medium 5.1)
- [CVE-2007-5171](https://insights.sbomify.com/CVE-2007-5171/): Missing authorization in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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