CVE-2026-59688
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 · uneditedAn OS Command Injection vulnerability in Progress Software LoadMaster, ECS Connection Manager, Object Scale Connection Manager, and MOVEit WAF allows an authenticated attacker with high privileges to execute arbitrary operating system commands on the affected appliance via the backup restore functionality, potentially resulting in complete system compromise.
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 confidenceThis is an OS Command Injection vulnerability in the backup restore functionality of multiple Progress Software products (LoadMaster, ECS Connection Manager, Object Scale Connection Manager, and MOVEit WAF). An attacker with high-privilege authentication can inject and execute arbitrary operating system commands through this feature, potentially achieving full system compromise.
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.63.3< 7.2.63.3< 7.2.63.3< 7.2.54.19>= 7.2.55.0, < 7.2.63.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Progress Software productCheck system inventory or running services for LoadMaster, ECS Connection Manager, Object Scale Connection Manager, or MOVEit WAF. Look for process names, installed packages, or service entries matching these product names.Affected if Any of these four products are installed on the system
-
Determine product versionUse the product-specific command or interface to retrieve the installed version. For LoadMaster, check the web UI version info or 'lmutil' tool. For others, consult the admin interface or check installed package metadata.Affected if Installed version falls within any known affected version range for the identified product
-
Verify backup restore feature accessibilityCheck if the backup/restore functionality is enabled in the administrative interface. Look for backup configuration pages or REST API endpoints related to restore operations.Affected if Backup restore feature is enabled and accessible to the authenticated user
-
Confirm administrative interface exposureReview network configuration to determine if the administrative web interface (typically ports 443, 8443, or product-specific ports) is exposed to untrusted networks. Check firewall rules and ACLs.Affected if Administrative interface is accessible from networks beyond trusted administrative workstations
-
Audit for suspicious backup restore activityReview system logs, audit logs, and web server logs for backup restore operations, especially those initiated at unusual times, from unusual sources, or containing unexpected parameters.Affected if Evidence exists of backup restore operations that were not initiated by authorized administrators
A user is affected if they run any of the four named Progress Software products with the backup restore feature enabled and the administrative interface accessible to authenticated high-privilege 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.
From vendor data7.2.54.197.2.63.3
Apply vendor-provided patches when available. Until then, strictly limit backup restore functionality to only necessary high-privilege users, implement additional network segmentation, and monitor for suspicious backup/restore operations.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.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,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59688 — 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-2026-59688 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