NVD / CVE Program· CNA SolarWinds

CVE-2024-28989: SolarWinds Web Help Desk Cryptographic Key Management Vulnerability

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

SolarWinds Web Help Desk was found to have a hardcoded cryptographic key that could allow the disclosure of sensitive information from the software.

MediumCVSS 5.5 · v3.1—No exploit No fix recorded

Hard-coded credentials

Published: Feb 11, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 21th percentile
CWE: CWE-321

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · SolarWinds: 5.5; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
solarwinds	web help desk	cpe:2.3:a:solarwinds:web_help_desk

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

solarwinds web help deskbefore 12.8.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (SolarWinds). Independent of NVD's CPE analysis and usually ahead of it.

SolarWinds Web Help Desk
- 12.8.4 and previous versionsaffected

Same product

solarwinds: all records

Other highest-scoring records for the same primary product.

CVE-2025-26399SolarWinds Web Help Desk Deserialization of Untrusted Data Privilege Escalation VulnerabilityKEV
96Now
CVE-2025-40551SolarWinds Web Help Desk Deserialization of Untrusted Data Remote Code Execution VulnerabilityKEV
94Now
CVE-2024-28987SolarWinds Web Help Desk Hardcoded Credential VulnerabilityKEV
94Now

Published before and after this one in the same product

← EarlierCVE-2024-28986Aug 13, 2024 · SolarWinds Web Help Desk Java Deserialization Remote Code Execution VulnerabilityKEV
94Now
← EarlierCVE-2024-45709Dec 10, 2024 · SolarWinds Web Help Desk Local File Read Vulnerability
22Monitor
Later →CVE-2025-26400Jul 29, 2025 · SolarWinds Web Help Desk XML External Entity Injection (XXE) Vulnerability
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope