CVE-2020-5560
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 · uneditedWL-Enq 1.11 and 1.12 allows remote attackers to execute arbitrary OS commands with the administrative privilege via unspecified vectors.
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 confidenceWL-Enq versions 1.11 and 1.12 contains a remote OS command injection vulnerability that allows unauthenticated remote attackers to execute arbitrary operating system commands with administrative privileges. The attack vector is unspecified in the available documentation, but the critical CVSS score (9.8) indicates a severe, easily exploitable flaw likely involving unsanitized input being passed to system calls.
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= 1.11= 1.12CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if WL-Enq is installedSearch for WL-Enq application files, services, or processes on the system. Common locations include /opt/, /usr/local/, or check running services for 'wl-enq' or similar process names.Affected if WL-Enq software is present on the system
-
Determine installed WL-Enq versionCheck the application's version information. Look for version files, examine the binary/application metadata, or query the application directly if it exposes version information via CLI flag (e.g., --version) or web interface.Affected if Installed version matches 1.11 or 1.12 exactly
-
Check if WL-Enq service is exposed to networkReview network configuration to determine if WL-Enq web interface or API is accessible from network interfaces. Check firewall rules, reverse proxy configurations, and listen addresses in the application configuration.Affected if The WL-Enq service is listening on a network-accessible interface (especially untrusted networks)
-
Verify authentication configurationExamine WL-Enq configuration files and authentication settings to confirm whether the command injection endpoint requires authentication. The CVE states unauthenticated attackers can exploit the flaw.Affected if The affected endpoint or functionality is accessible without authentication
Your environment is affected if WL-Enq versions 1.11 or 1.12 are installed and the service is network-accessible without requiring authentication, as the command injection can be exploited by any unauthenticated remote attacker.
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 dataSince specific vectors are not disclosed, implement defense-in-depth: restrict network access to WL-Enq to only trusted sources, apply vendor patches when available, disable the service if not needed, and monitor for Indicators of Compromise. If the application must remain in production, consider deploying a WAF with virtual patching capabilities.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5560 — 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-2020-5560 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