# CVE-2004-2524: Information disclosure in n/a

> Remote attackers can obtain plaintext username and password credentials by manipulating parameters in clogin.php, exposing sensitive authentication data.

- **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:** 25 Oct 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3gmr-q2mv-97r5

## What is CVE-2004-2524?

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

### Official description

clogin.php in Benchmark Designs' WHM AutoPilot 2.4.5 and earlier allows remote attackers to obtain plaintext username and password credentials by using the clogin_e and base64_encode functions to encode the desired user ID in the c parameter, then read the plaintext values in the resulting form.

## Which versions are affected by CVE-2004-2524?

It affects 1 product.


Products: Whm Autopilot Whm Autopilot.

## How do I fix CVE-2004-2524?

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

## Is CVE-2004-2524 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2524 and fix it if it is affected.

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

## Sources

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

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