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

> Remote authenticated administrators can obtain cleartext user passwords by viewing HTML source in MailEnable Professional.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-54wp-7535-r37v

## What is CVE-2006-6964?

CVE-2006-6964 is a medium-severity vulnerability in n/a, published on 29 Jan 2007. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

MailEnable Professional before 1.78 provides a cleartext user password when an administrator edits the user's settings, which allows remote authenticated administrators to obtain sensitive information by viewing the HTML source.

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

It affects 1 product.


Products: Mailenable Mailenable Professional.

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

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

## Is CVE-2006-6964 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2222](https://insights.sbomify.com/CVE-2005-2222/): Other in n/a (critical 10.0)
- [CVE-2005-2278](https://insights.sbomify.com/CVE-2005-2278/): Memory corruption in n/a (high 7.2)
- [CVE-2007-0652](https://insights.sbomify.com/CVE-2007-0652/): Cross-site request forgery in n/a (medium 5.1)
- [CVE-2006-0503](https://insights.sbomify.com/CVE-2006-0503/): Denial of service in n/a (medium 5.0)
- [CVE-2005-2223](https://insights.sbomify.com/CVE-2005-2223/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6964 is a medium-severity vulnerability in n/a, published on 29 Jan 2007. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-6964 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-6964/ (Markdown: https://insights.sbomify.com/CVE-2006-6964/index.md)
```

## Sources

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

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