dbcve.org
Whatsup GoldApplication · Progress

CVE-2022-42711

CRITICAL · 9.6 CVSS v3.1 Published 2022-10-12
Fix available
A fix is available. Upgrade to 22.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Progress WhatsUp Gold before 22.1.0, an SNMP MIB Walker application endpoint failed to adequately sanitize malicious input. This could allow an unauthenticated attacker to execute arbitrary code in a victim's browser.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SNMP MIB Walker application endpoint in Progress WhatsUp Gold before version 22.1.0 fails to adequately sanitize malicious input, allowing an unauthenticated attacker to inject arbitrary JavaScript code that executes in victims' browsers (stored XSS).

MitigationUpgrade to WhatsUp Gold version 22.1.0 or later to obtain the patch that addresses the input sanitization failure in the SNMP MIB Walker endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Whatsup GoldApplication
Affected:< 22.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WhatsUp Gold is installed
    Check the Windows Programs and Features list, or look for the WhatsUp Gold installation directory (typically in C:\Program Files\Progress\WhatsUp Gold or C:\Program Files (x86)\Progress\WhatsUp Gold)
    Affected if WhatsUp Gold software is present on the system
  2. Determine the installed version number
    Check the version of the WhatsUp Gold installation - this is typically visible in the Programs and Features list, or can be found in the application's About/Help section, or by locating the main executable's file properties
    Affected if The installed version is lower than 22.1.0 (for example, 22.0.x, 21.x, or earlier)
  3. Verify the SNMP MIB Walker endpoint is accessible
    Confirm that the web interface for WhatsUp Gold is running and the SNMP MIB Walker functionality is available - typically accessed via the web UI under Network > Tools or similar paths
    Affected if The SNMP MIB Walker web endpoint is exposed and accessible (even without authentication, since the vulnerability allows unauthenticated injection)
  4. Review web server or application logs for suspicious activity
    Examine WhatsUp Gold web logs (typically found in the installation directory under Log or App_Data folders) for unusual patterns, especially entries containing script tags or JavaScript-like content in MIB-related requests
    Affected if Logs contain entries with injected script tags or unusual characters in SNMP MIB Walker parameters that may indicate exploitation attempts

A user is affected if WhatsUp Gold is installed with a version lower than 22.1.0 AND the SNMP MIB Walker web endpoint is accessible and could accept malicious input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 22.1.0 or later
Fixed in 22.1.0
Interim mitigation

Upgrade to WhatsUp Gold version 22.1.0 or later to obtain the patch that addresses the input sanitization failure in the SNMP MIB Walker endpoint.

Recommended fix High confidence

22.1.0

  1. Identify the current WhatsUp Gold version by checking the installation or admin console
  2. Create a complete backup of the WhatsUp Gold installation directory and database
  3. Download WhatsUp Gold version 22.1.0 or later from the official Progress download portal
  4. Stop the WhatsUp Gold services before performing the upgrade
  5. Install the upgrade following Progress standard upgrade procedures
  6. Start the WhatsUp Gold services after upgrade completion
  7. Verify the upgrade was successful by checking the version number in the admin interface
  8. Test that the SNMP MIB Walker functionality is operational after the upgrade
Caveat Standard upgrade precautions apply - ensure backups are verified before proceeding, and test in a non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Whatsup Gold Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42711 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data