CVE-2020-12427
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 · uneditedThe Western Digital WD Discovery application before 3.8.229 for MyCloud Home on Windows and macOS is vulnerable to CSRF, with impacts such as stealing data, modifying disk contents, or exhausting disk space.
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 confidenceThe WD Discovery application before version 3.8.229 for MyCloud Home on Windows and macOS contains a Cross-Site Request Forgery (CSRF) vulnerability that allows remote attackers to induce authenticated users to perform unintended actions, including stealing data, modifying disk contents, or exhausting disk space.
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< 3.8.229CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Check if WD Discovery is installed on WindowsOpen Control Panel > Programs and Features, or check the installation directory (typically C:\Program Files\Western Digital\WD Discovery)Affected if WD Discovery appears in the installed programs list or the directory exists
-
Check if WD Discovery is installed on macOSOpen Finder > Applications folder and look for 'WD Discovery.app', or run: ls /Applications | grep -i 'WD Discovery'Affected if WD Discovery.app exists in the Applications folder
-
Determine the installed version on WindowsRight-click the WD Discovery executable or DLL, select Properties, then go to the Details tab to view the Product VersionAffected if The version displayed is lower than 3.8.229
-
Determine the installed version on macOSRight-click WD Discovery.app > Get Info, or right-click the app > Show Package Contents and check Info.plist for CFBundleShortVersionStringAffected if The version displayed is lower than 3.8.229
-
Verify via command line on WindowsOpen PowerShell and run: Get-ItemProperty 'C:\Program Files\Western Digital\WD Discovery\WDDiscovery.exe' | select -expand VersionInfoAffected if The reported version is lower than 3.8.229
If WD Discovery is installed and the version is below 3.8.229, the environment is vulnerable to CSRF attacks via the web interface.
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 data3.8.229
Implement anti-CSRF tokens for all state-changing operations and validate Origin/Referer headers in HTTP requests to prevent forged requests. Users should update to version 3.8.229 or later.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12427 — 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-12427 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