CVE-2019-9951
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 · uneditedWestern Digital My Cloud, My Cloud Mirror Gen2, My Cloud EX2 Ultra, My Cloud EX2100, My Cloud EX4100, My Cloud DL2100, My Cloud DL4100, My Cloud PR2100 and My Cloud PR4100 firmware before 2.31.174 is affected by an unauthenticated file upload vulnerability. The page web/jquery/uploader/uploadify.php can be accessed without any credentials, and allows uploading arbitrary files to any location on the attached storage.
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 confidenceUnauthenticated file upload vulnerability in Western Digital My Cloud devices allows remote attackers to upload arbitrary files to any location on attached storage via the web/jquery/uploader/uploadify.php endpoint without any authentication, achieving critical severity (CVSS 9.8).
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< 2.31.174< 2.31.174< 2.31.174< 2.31.174< 2.31.174< 2.31.174< 2.31.174< 2.31.174CVSS 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.0/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 the device modelAccess the device web interface and look for the model name in the dashboard or system settings, or query the device's API endpoint for model informationAffected if The device is one of: My Cloud Mirror Gen 2, My Cloud Ex2 Ultra, My Cloud Ex2100, My Cloud Ex4100, My Cloud Dl2100, My Cloud Dl4100, My Cloud Pr2100, or My Cloud Pr4100
-
Check the installed firmware versionIn the device web interface, navigate to Settings > About or Settings > System > Firmware Update to view the current firmware version. Alternatively, access the API endpoint /api/1.0/rest/smart_mode/Status or check the version via SSH if enabledAffected if The firmware version is less than 2.31.174 (for example, 2.30.x, 2.29.x, or earlier)
-
Verify web interface accessibilityAttempt to access the device web login page from an external or untrusted network using the device IP or hostname (for example, http://<device-ip>/)Affected if The web management interface is accessible from network segments that are not restricted or are considered untrusted
-
Check for the vulnerable endpoint exposureAttempt to access the path /web/jquery/uploader/uploadify.php on the device (for example, http://<device-ip>/web/jquery/uploader/uploadify.php) and observe if the script respondsAffected if The endpoint returns an HTTP response (even if it returns an error) indicating the script exists and is accessible without authentication
The device is affected if it is a Western Digital My Cloud model listed in the affected products and runs firmware version lower than 2.31.174, with the web interface or the specific vulnerable endpoint accessible from the network.
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 · scoped2.31.174
Upgrade affected devices to firmware version 2.31.174 or later. If immediate patching is not possible, restrict network access to the vulnerable endpoint and device management interfaces.
Firmware version 2.31.174 or later for the specific My Cloud model
- 1. Identify the specific My Cloud model (e.g., My Cloud PR4100, My Cloud Ex2 Ultra, etc.)
- 2. Access the My Cloud dashboard by navigating to the device's IP address in a web browser
- 3. Go to Settings > Firmware or Settings > System to check the current firmware version
- 4. Verify the current version is below 2.31.174
- 5. Download the firmware update (version 2.31.174 or later) from the official Western Digital support site (support.wdc.com) for your specific model
- 6. In the My Cloud dashboard, navigate to Settings > Firmware Update or Manual Update
- 7. Upload the downloaded firmware file and initiate the update
- 8. Wait for the firmware to upload, install, and for the device to reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9951 — 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-2019-9951 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