dbcve.org
Multi Tenant LoadmasterApplication · Progress

CVE-2025-1758

HIGH · 8.8 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to 7.2.61.1 or later.
See remediation →
93/100
Remediation priority · Urgent
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
Improper Input Validation vulnerability in Progress LoadMaster allows : Buffer OverflowThis issue affects: * LoadMaster: 7.2.40.0 and above * ECS: All versions * Multi-Tenancy: 7.1.35.4 and above

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

Improper input validation in Progress LoadMaster products allows a buffer overflow condition. The vulnerability affects LoadMaster (7.2.40.0+), ECS (all versions), and Multi-Tenancy (7.1.35.4+), potentially allowing attackers to trigger the overflow through malformed input.

MitigationApply vendor-provided patches for affected LoadMaster, ECS, and Multi-Tenancy versions. Until patches are available, restrict network access to management interfaces and monitor for indicators of exploit attempts.

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
Multi Tenant LoadmasterApplication
Affected:>= 7.1.35.4
LoadmasterOperating system
Affected:>= 7.2.40.0, < 7.2.61.1

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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 the installed Progress product
    Access the LoadMaster administrative interface or check system documentation to determine if the deployed product is LoadMaster, ECS (Elastic Container Service), or Multi-Tenant LoadMaster.
    Affected if The product is any of LoadMaster (any version), ECS (any version), or Multi-Tenant LoadMaster (any version)
  2. Check LoadMaster version number
    Log into the LoadMaster management interface and navigate to System Configuration > System Administration > Version/License, or run 'lmutil --version' from the command line if available.
    Affected if The installed version is 7.2.40.0 or higher but lower than 7.2.61.1
  3. Check Multi-Tenant LoadMaster version number
    Access the Multi-Tenant LoadMaster management console and locate the version information, typically found in the About or System Info section.
    Affected if The installed version is 7.1.35.4 or higher
  4. Confirm ECS installation
    Review deployed ECS instances or containers to determine if Progress ECS software is installed. Check container images or package inventories for 'Progress ECS' or 'LoadMaster ECS' components.
    Affected if Progress ECS is installed on the system (all versions are affected)
  5. Verify management interface exposure
    Review network configuration to determine if the LoadMaster management interface (typically ports 443, 8443) is accessible from untrusted networks. Check firewall rules and access control lists.
    Affected if Management interface is exposed to the internet or untrusted networks

You are affected if you are running LoadMaster versions 7.2.40.0 through 7.2.61.0, Multi-Tenant LoadMaster version 7.1.35.4 or higher, or any version of ECS, especially if the management interface is network-accessible.

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

Apply vendor-provided patches for affected LoadMaster, ECS, and Multi-Tenancy versions. Until patches are available, restrict network access to management interfaces and monitor for indicators of exploit attempts.

Recommended fix Moderate confidence

LoadMaster 7.2.61.1 or later; Multi-Tenant LoadMaster: contact Progress for exact fixed 7.1.x release

  1. 1. Identify the exact LoadMaster version currently installed using the web interface (Support > System History) or via CLI: "lmutil lmver"
  2. 2. For LoadMaster: Upgrade to version 7.2.61.1 or later by downloading the update from the Progress Customer Portal or authorized distribution channel
  3. 3. For Multi-Tenant LoadMaster: Upgrade to the corresponding fixed release for the 7.1.x branch (contact Progress support for exact version if not explicitly listed in security advisory)
  4. 4. For ECS: Contact Progress Support for specific patch or upgrade path since all versions are affected
  5. 5. After upgrade, verify the new version is running: Support > System History in the LoadMaster web UI
  6. 6. Review release notes for 7.2.61.1 to ensure no configuration changes are required for your deployment
Caveat Review LoadMaster 7.2.61.1 release notes for any configuration or feature changes before upgrading in production environments

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

Fix this in Multi Tenant Loadmaster Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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