# CVE-2025-30248: Other in WD Discovery

> A local attacker can execute arbitrary code by placing a malicious DLL in the WD Discovery installer's search path.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-5899-4rc7-89rh

## What is CVE-2025-30248?

CVE-2025-30248 is a high-severity vulnerability in Western Digital WD Discovery, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

DLL hijacking in the WD Discovery Installer in Western Digital WD Discovery 5.2.730 on Windows allows a local attacker to execute arbitrary code via placement of a crafted dll in the installer's search path.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2025-30248?


## How do I fix CVE-2025-30248?

No fix has been published for CVE-2025-30248 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-30248 being exploited?

There is no known exploitation of CVE-2025-30248 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30248 and fix it if it is affected.

What it is: CVE-2025-30248 is a high-severity vulnerability in Western Digital WD Discovery, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-30248 in the wild and no public exploit code.

Affected product: Western Digital WD Discovery. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-30248/ (Markdown: https://insights.sbomify.com/CVE-2025-30248/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-30248
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-30248
- OSV: https://osv.dev/vulnerability/CVE-2025-30248

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-30248/
Summaries are generated and may contain mistakes; the official description above is the record.