dbcve.org
Mycloud.comApplication · Westerndigital

CVE-2020-8960

MEDIUM · 6.1 CVSS v3.1 Published 2020-02-20
Fix available
A fix is available. Upgrade to 2.2.0-134 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Western Digital mycloud.com before Web Version 2.2.0-134 allows XSS.

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

Cross-site scripting (XSS) vulnerability in Western Digital mycloud.com web interface. The vulnerability exists in versions prior to Web Version 2.2.0-134, allowing attackers to inject malicious scripts into the web application.

MitigationUpgrade the WD My Cloud firmware/web interface to version 2.2.0-134 or later to remediate the XSS vulnerability.

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
Mycloud.comApplication
Affected:< 2.2.0-134

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Check WD My Cloud web interface version
    Log into the WD My Cloud web interface (typically at mycloud.com or the device's local IP address). Navigate to Settings > About or Settings > System to find the Web Version or Firmware Version information.
    Affected if The displayed Web Version is less than 2.2.0-134 (for example, 2.2.0-100 or earlier)
  2. Verify version via device firmware
    Access the device's administrative panel and locate the firmware version information, which typically includes the web interface version.
    Affected if The firmware/web version shown is below 2.2.0-134
  3. Check for XSS exposure in web parameters
    If you have access to the device's web interface, examine URL parameters and form inputs in the mycloud.com interface for unvalidated input reflection.
    Affected if User-supplied input in web requests is reflected back without proper encoding or sanitization, indicating the XSS vulnerability is present

A user is affected if their WD My Cloud device runs a web interface version earlier than 2.2.0-134, as confirmed by checking the version displayed in the device settings or about page.

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.

From vendor data
Upgrade available Upgrade to 2.2.0-134 or later
Fixed in 2.2.0-134
Interim mitigation

Upgrade the WD My Cloud firmware/web interface to version 2.2.0-134 or later to remediate the XSS vulnerability.

Fix this in Mycloud.com Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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