Threats / Progress / CVE-2024-4885
CVE-2024-4885
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Progress WhatsUp Gold vulnerability
Progress WhatsUp Gold contains a path traversal vulnerability (CWE-22) allowing unauthenticated remote code execution. The vulnerability is actively exploited in the wild.
Verdict
Today item — known-exploited.
An unauthenticated attacker can exploit a path traversal flaw in WhatsUp Gold to execute arbitrary code remotely. Active exploitation in the wild and high EPSS score (0.94) indicate immediate risk to unpatched deployments.
CISA KEV Yes · 2025-03-035EPSS 0.99288 (verify live)6Exploit Weaponized · public PoC7CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
409 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-03-03).
Probability (EPSS)
EPSS 0.99288 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Progress, WhatsUp Gold. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 251 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request using path traversal sequences to bypass file access restrictions in WhatsUp Gold.
Business
Attackers gain initial access to the monitoring infrastructure without authentication credentials.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the path traversal to write or execute arbitrary code on the WhatsUp Gold server.
Business
The organization loses control of its network monitoring system, a critical infrastructure component.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access and move laterally through the monitored network using the compromised monitoring platform.
Business
Attackers gain visibility into and control over the entire monitored network, enabling data theft or further compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by ProgressSoftwareCNA