basicsecurity.net
Proof, not just disclosure.
Threats / Progress / CVE-2024-6670
CVE-2024-6670 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-07

Progress WhatsUp Gold vulnerability

Progress WhatsUp Gold contains a SQL injection vulnerability allowing unauthenticated attackers to retrieve encrypted user passwords when configured with a single user account.

Verdict

Today item, not a backlog item.

An unauthenticated remote attacker can exploit SQL injection to extract encrypted credentials from WhatsUp Gold deployments, potentially leading to authentication bypass and lateral movement within monitored infrastructure.

CISA KEV Yes · 2024-09-163Ransomware use Flagged3EPSS 0.94468 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-09-16), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.94468 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Progress, WhatsUp Gold. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-89 · SQL InjectionInjection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No threat-actor attribution is established from the public feed 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious SQL query and send it through an unauthenticated application endpoint to bypass authentication checks.
Business
The application fails to validate user input before executing database queries, creating an entry point for unauthorized data access.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I extract encrypted password hashes from the database by manipulating SQL syntax to retrieve credential records.
Business
Sensitive authentication material is exposed, compromising the confidentiality of user accounts and administrative access.
3

Lateral reach — past segmentation narrative 3

Attacker
I use the recovered encrypted credentials as a stepping stone to compromise additional systems or escalate privileges within the monitored environment.
Business
Attackers gain persistent access to critical infrastructure monitoring systems, enabling reconnaissance for ransomware deployment or data exfiltration campaigns.
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’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • CWE weakness mapping (NVD)
  • Catalogued by ProgressSoftware (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by ProgressSoftwareCNA
    Credited with finding itSina Kheirkhah (@SinSinology) of Summoning Team (@SummoningTeam) working with Trend Micro Zero Day Initiativefinder