CVE-2024-6670
In WhatsUp Gold versions released before 2024.0.0, a SQL Injection vulnerability allows an unauthenticated attacker to retrieve the users encrypted password.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Yes. SQL injection puts SQL syntax into a request parameter, and WAF signatures recognise that syntax well.
Also consider: parameterized queries · ORM
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-6670 being exploited?
Yes. CVE-2024-6670 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-6670?
CVE-2024-6670 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-6670?
Yes. A fix has been recorded for CVE-2024-6670. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-6670 affect?
CVE-2024-6670 affects progress:whatsup_gold. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 2023.1.0 and < 2024.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 Metasploit module · 1 GitHub proof of concept · 1 Nuclei template
- auxiliary/admin/http/whatsup_gold_sqli · auxiliary · normal
- WhatsUp Gold HasErrors SQL Injection - Authentication Bypass · detection template · critical
- sinsinology/CVE-2024-6670 · 35 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 27 Jan 2025 (SSVC 2.0.3).
timeline
- 29 Aug 2024Published
- 30 Aug 2024First proof-of-concept repository on GitHub (unvetted) · same day later
- 16 Sept 2024Added to CISA KEV (exploited in the wild) · 17 days later
- 7 Oct 2024CISA remediation due date (US federal agencies) · 21 days later
- 27 Jan 2025CISA SSVC assessment: exploitation active · 113 days (about 4 months) later
- 21 Oct 2025CVE record last updated · 267 days (about 9 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Advisorycommunity.progress.com /s/article/WhatsUp-Gold-Security-Bulletin-August-2024
- Linkprogress.com /network-monitoring
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-6670
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.