dbcve.org
Whatsup GoldApplication · Progress

CVE-2025-2572

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-14
Fix available
A fix is available. Upgrade to 24.0.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 WhatsUp Gold versions released before 2024.0.3, a database manipulation vulnerability allows an unauthenticated attacker to modify the contents of WhatsUp.dbo.WrlsMacAddressGroup.

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 · moderate confidence

An unauthenticated attacker can manipulate the contents of the WhatsUp.dbo.WrlsMacAddressGroup database table in WhatsUp Gold versions prior to 2024.0.3. This database manipulation vulnerability likely stems from insufficient input validation or authentication checks on database interaction endpoints, allowing unauthorized modification of wireless MAC address group data.

MitigationUpgrade WhatsUp Gold to version 2024.0.3 or later to obtain the vendor patch. Additionally, audit the WrlsMacAddressGroup table for unauthorized or unexpected modifications and review access logs for indicators of exploitation.

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:< 24.0.3

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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. Determine your WhatsUp Gold version
    Access the WhatsUp Gold admin interface and navigate to Help > About, or check the installation directory for version information. Alternatively, query the database for version metadata if accessible.
    Affected if The installed version is lower than 24.0.3 (for example, 24.0.2, 23.x, or earlier releases).
  2. Verify the WrlsMacAddressGroup table exists
    Connect to the WhatsUp Gold SQL database and query: SELECT * FROM WhatsUp.dbo.WrlsMacAddressGroup. This table stores wireless MAC address group configurations.
    Affected if The table exists and is accessible, which is expected in all standard installations of affected versions.
  3. Inspect the WrlsMacAddressGroup table for unauthorized changes
    Query the table contents and compare against known-good configurations or backups. Look for unexpected MAC address entries, new groups, or modified settings that were not intentionally created by administrators.
    Affected if Unexpected or unauthorized records exist in the table that were not added by legitimate administrators.
  4. Review database access logs and application logs
    Examine WhatsUp Gold logs, SQL Server logs, and any web server logs for unusual queries or connections targeting the WrlsMacAddressGroup table, especially from unauthenticated or unexpected sources.
    Affected if Logs show suspicious or unauthorized database queries to this table from sources outside expected administrative IP ranges.

Your environment is affected if you are running WhatsUp Gold version 24.0.2 or earlier, and particularly if the WrlsMacAddressGroup table shows unexpected modifications or logs indicate unauthorized database access.

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 24.0.3 or later
Fixed in 24.0.3
Interim mitigation

Upgrade WhatsUp Gold to version 2024.0.3 or later to obtain the vendor patch. Additionally, audit the WrlsMacAddressGroup table for unauthorized or unexpected modifications and review access logs for indicators of exploitation.

Recommended fix High confidence

WhatsUp Gold 24.0.3

  1. 1. Obtain WhatsUp Gold version 24.0.3 or later from the official Progress download site (www.progress.com or docs.progress.com)
  2. 2. Create a complete backup of your WhatsUp Gold database and configuration files before upgrading
  3. 3. Install the WhatsUp Gold 24.0.3 upgrade following the standard Progress upgrade documentation
  4. 4. After installation, verify the web interface is accessible and all services are running
  5. 5. Confirm that the WhatsUp.dbo.WrlsMacAddressGroup table can only be modified by authenticated users with proper permissions
Caveat Review the WhatsUp Gold 24.0.3 release notes for any migration considerations or configuration changes before upgrading

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

Fix this in Whatsup Gold Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2572 — 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-2025-2572 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