# CVE-2005-4661: Information disclosure in n/a

> Campsite CMS sends unencrypted MySQL passwords in email notifications, allowing remote attackers to sniff 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:** 16 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-22m9-jhmf-fc7x

## What is CVE-2005-4661?

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

### Official description

The notifyendsubs cron job in Campsite before 2.3.3 sends an e-mail message containing a certain unencrypted MySQL password, which allows remote attackers to sniff the password.

## Which versions are affected by CVE-2005-4661?

It affects 1 product.


Products: Campware.org Campsite.

## How do I fix CVE-2005-4661?

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

## Is CVE-2005-4661 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5912](https://insights.sbomify.com/CVE-2006-5912/): Unspecified vulnerability in Campware Campsite before 2.6.2 has unknown impact and attack vectors, related to a "Security fix for you-know-w (critical 10.0)
- [CVE-2010-1867](https://insights.sbomify.com/CVE-2010-1867/): SQL injection in n/a (high 7.5)
- [CVE-2009-2183](https://insights.sbomify.com/CVE-2009-2183/): Path traversal in n/a (high 7.5)
- [CVE-2006-5910](https://insights.sbomify.com/CVE-2006-5910/): Code injection in n/a (high 7.5)
- [CVE-2006-5911](https://insights.sbomify.com/CVE-2006-5911/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4661 and fix it if it is affected.

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

## Sources

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

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