CVE-2025-13447
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 confidenceOS command injection vulnerability in Progress LoadMaster API allows authenticated attackers with User Administration permissions to execute arbitrary commands by exploiting unsanitized input in API parameters, resulting in remote code execution on the LoadMaster appliance.
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.54.16< 7.2.62.2= 7.2.62.1< 7.1.35.15CVSS 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 installed LoadMaster product and versionAccess the LoadMaster web UI (typically https://<host>/) and navigate to System Configuration > System Administration > Updates & Licensing > Version. Alternatively, check via CLI: 'lmutil -v' or review the About page in the web interface.Affected if Installed version is earlier than 7.2.54.16, earlier than 7.2.62.2, or equals exactly 7.2.62.1 for the affected products listed.
-
Confirm API interface is accessibleVerify the LoadMaster REST API is exposed. Check if port 443/8443 is open externally or if the API endpoint responds to requests at https://<host>/api/v1/ or similar paths. Review network firewall rules for API port exposure.Affected if The LoadMaster API is reachable from network segments where untrusted users have access.
-
Verify User Administration role existsLog into the LoadMaster web UI and navigate to Users & Security > User Administration. Check if any users are assigned the 'User Administration' role or if the role is present in the configuration.Affected if The User Administration role is defined or any user account has User Administration permissions assigned.
-
Review API access controlsCheck API authentication configuration in System Configuration > Rest API > API Access. Verify whether API access requires strong authentication and if API keys or tokens are properly secured.Affected if API access is enabled without strict authentication controls or API credentials are shared broadly.
-
Check for suspicious command execution logsReview LoadMaster system logs (System Monitoring > Log Files > System Logs) and security logs for entries containing shell commands, unexpected API calls, or privilege escalation events, particularly around API endpoints.
Your environment is affected if you are running any of the listed Progress products at versions lower than the fixed releases AND the LoadMaster API is accessible with User Administration role permissions enabled for your users.
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
Apply vendor-provided patches when released. Until then, strictly limit User Administration permissions to trusted personnel only and restrict API access through network segmentation.
7.2.62.2 or higher (7.1.35.15 or higher for Multi Tenant Hypervisor)
- 1. Identify the affected Progress product (LoadMaster, Moveit WAF, Connection Manager, or Multi Tenant Hypervisor) currently deployed
- 2. Determine the current installed version of the product
- 3. For LoadMaster, Moveit WAF, Connection Manager For Objectscale, or Ecs Connection Manager: Upgrade to version 7.2.62.2 or later
- 4. For Multi Tenant Hypervisor: Upgrade to version 7.1.35.15 or later
- 5. Verify the upgrade was successful by confirming the new version number in the product interface
- 6. Test that critical functionality remains operational after the upgrade
- 7. Restrict API access to only trusted users and follow the principle of least privilege for "User Administration" permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13447 — 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-13447 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