# CVE-2024-28987: SolarWinds Web Help Desk Hardcoded Credential

> Remote unauthenticated attackers can access internal functionality and modify data in SolarWinds Web Help Desk due to hardcoded credentials.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 15 Oct 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-4jq7-4qmf-m333

## What is CVE-2024-28987?

CVE-2024-28987 is a critical vulnerability in SolarWinds Web Help Desk, published on 21 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SolarWinds Web Help Desk (WHD) software is affected by a hardcoded credential vulnerability, allowing remote unauthenticated user to access internal functionality and modify data.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2024-28987?

It affects 1 product.


Products: Solarwinds Web Help Desk.

## How do I fix CVE-2024-28987?

No fix has been published for CVE-2024-28987 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 Nov 2024.

## Is CVE-2024-28987 being exploited?

Yes. Attackers have exploited CVE-2024-28987 in the wild since at least 15 Oct 2024.

Public exploit code:

- Web Help Desk Hardcoded Credential Vulnerability (CVE-2024-28987) (github_poc): https://github.com/gh-ost00/CVE-2024-28987-POC
- Proof of Concept Exploit for CVE-2024-28987: SolarWinds Web Help Desk Hardcoded Credential Vulnerability (github_poc): https://github.com/horizon3ai/CVE-2024-28987
- Proof of Concept Exploit for CVE-2024-28987: SolarWinds Web Help Desk Hardcoded Credential Vulnerability (github_poc): https://github.com/alecclyde/CVE-2024-28987
- **CVE-2024-28987** is a critical vulnerability in SolarWinds Web Help Desk (WHD) that allows remote attackers to access sensitive ticket information using **hardcoded credentials**. This vulnerability has a **CVSS score of 9.1 (Critical)** and is actively being exploited in the wild. (github_poc): https://github.com/Darabium/CVE-2024-28987
- SolarWinds Web Help Desk Backdoor (CVE-2024-28987) (metasploit)
- SolarWinds Web Help Desk - Hardcoded Credential (nuclei): http/cves/2024/CVE-2024-28987.yaml

## Other vulnerabilities in SolarWinds Web Help Desk

- [CVE-2025-40551](https://insights.sbomify.com/CVE-2025-40551/): SolarWinds Web Help Desk Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2025-26399](https://insights.sbomify.com/CVE-2025-26399/): SolarWinds Web Help Desk Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2024-28986](https://insights.sbomify.com/CVE-2024-28986/): SolarWinds Web Help Desk Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2025-40536](https://insights.sbomify.com/CVE-2025-40536/): SolarWinds Web Help Desk Security Control Bypass (high 8.1, exploited in the wild)
- [CVE-2026-28323](https://insights.sbomify.com/CVE-2026-28323/): SolarWinds Web Help Desk SAML Authentication Bypass Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28987 and fix it if it is affected.

What it is: CVE-2024-28987 is a critical vulnerability in SolarWinds Web Help Desk, published on 21 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-28987 in the wild since at least 15 Oct 2024.

Affected product: SolarWinds Web Help Desk. 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-2024-28987/ (Markdown: https://insights.sbomify.com/CVE-2024-28987/index.md)
```

## Sources

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

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