CVE-2025-13444
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 · uneditedOS Command Injection Remote Code Execution Vulnerability in API in Progress LoadMaster allows an authenticated attacker with “User Administration” permissions to execute arbitrary commands on the LoadMaster appliance by exploiting unsanitized input in the API input parameters
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 confidenceAn OS command injection vulnerability exists in the Progress LoadMaster API where unsanitized input in API parameters allows an authenticated attacker with User Administration permissions to execute arbitrary OS commands on the LoadMaster appliance, achieving remote code execution.
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< 7.2.62.2< 7.2.62.2= 7.2.62.1< 7.1.35.15< 7.2.54.16>= 7.2.55.0, < 7.2.62.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the LoadMaster product and versionAccess the LoadMaster web interface (typically at the main login page) or check the version via the API endpoint. The version is usually displayed in the web interface footer or available via the /api/version endpoint.Affected if The installed version is less than 7.2.54.16, or less than 7.2.62.2 for products in the 7.2.x line, or less than 7.1.35.15 for Multi Tenant Hypervisor.
-
Confirm the API interface is accessibleVerify the LoadMaster API is exposed by attempting to access the API endpoint (typically /api/ or /rest/api/) from an internal network location. Check network configurations to see if the API port (usually 443 or 8443) is listening.Affected if The LoadMaster API is reachable from the network where potential attackers could send requests.
-
Audit User Administration accountsLog into the LoadMaster web interface and navigate to the User Administration section (or Users/Accounts menu). Review the list of accounts that have been granted User Administration or equivalent elevated permissions.Affected if There are user accounts with User Administration permissions, especially accounts that are unused, default, or shared.
-
Check API access credentialsReview the same User Administration section to identify which users have API access enabled. Look for users with both User Administration permissions and API access capability.Affected if Any account with User Administration permissions also has API access enabled.
-
Review logs for suspicious API activityExamine LoadMaster system logs and API access logs for any API calls that include unusual parameter patterns, especially those containing shell metacharacters like ; | & $ ` or command-like strings. Check the Audit Logs or System Logs section in the web interface.Affected if Log entries show API requests with suspicious patterns that could indicate command injection attempts.
A user is affected if their LoadMaster version falls within the vulnerable ranges AND the API is accessible with User Administration permissions available.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.1.35.157.2.54.167.2.62.2
Implement strict input validation and sanitization on all API parameters to prevent command injection, and apply vendor patches when available. Additionally, limit and audit User Administration permissions to reduce the attack surface.
Upgrade to LoadMaster version 7.2.62.2 or later (or 7.2.54.16 or later for older branches); Multi Tenant Hypervisor to 7.1.35.15 or later
- Identify the current version of the affected LoadMaster or related product by checking the web management interface or using the version check command
- Backup the current LoadMaster configuration before proceeding with any upgrade
- Download the fixed version (7.2.62.2 or later for LoadMaster/Connection Managers; 7.1.35.15 or later for Multi Tenant Hypervisor) from the official Progress Software download portal or support site
- Access the LoadMaster administrative interface and navigate to the System Configuration > System Update section
- Upload the downloaded update/package and initiate the upgrade process
- After upgrade completes, verify the new version is running and confirm all services are operational
- Review user permissions - ensure only trusted administrators have 'User Administration' permissions to reduce attack surface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13444 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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