Skip to content
Fencer Vulns
critical 9.8

CVE-2024-6670 kev+ ransomware in the critical feed json

WhatsUp Gold HasErrors SQL Injection Authentication Bypass Vulnerability

published 2024-08-29 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-48017

cvss
9.8
version 3.1, CNA
cisa kev
Exploited
added 2024-09-16, used in ransomware
epss
92.9%
EPSS 92.9% chance of exploitation in 30 days, percentile 99.8%
public exploits
1
Metasploit, plus a Nuclei check

Summary

In WhatsUp Gold versions released before 2024.0.0, a SQL Injection vulnerability allows an unauthenticated attacker to retrieve the users encrypted password.

Patch / fix

cisa required action Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

  • Progress Software Corporation WhatsUp Gold 2024.0.0
  • progress whatsupgold 2024.0.0

Timeline

  1. First public exploit (Metasploit auxiliary/admin/http/whatsup_gold_sqli)
  2. Published
  3. Added to CISA KEV
  4. CISA patch deadline
  5. CISA SSVC: exploitation active

Known exploited

Added
2 y ago
Patch by
2024-10-07 (2 y ago)
Ransomware
Known to be used in ransomware campaigns
Required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Vendor, product
Progress, WhatsUp Gold
CISA name
Progress WhatsUp Gold SQL Injection Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
21 mo ago

Exploit prediction

92.91% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Progress Software Corporation WhatsUp Gold
  • progress whatsupgold

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.