# CVE-2025-8978: D-Link DIR-619L boa FirmwareUpgrade data authenticity

> Attackers can bypass firmware authenticity checks on unsupported D-Link routers to potentially execute arbitrary code or escalate privileges.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 14 Aug 2025
- **Also known as:** GHSA-5j9f-jgfq-46gx

## What is CVE-2025-8978?

CVE-2025-8978 is a high-severity vulnerability in Dlink Dir-619l Firmware, published on 14 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was determined in D-Link DIR-619L 6.02CN02. Affected is the function FirmwareUpgrade of the component boa. The manipulation leads to insufficient verification of data authenticity. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Dlink Dir-619l Firmware.

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

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

## Is CVE-2025-8978 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8978 exists.

## Other vulnerabilities in Dlink Dir-619l Firmware

- [CVE-2025-55599](https://insights.sbomify.com/CVE-2025-55599/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-55602](https://insights.sbomify.com/CVE-2025-55602/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-55611](https://insights.sbomify.com/CVE-2025-55611/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-43869](https://insights.sbomify.com/CVE-2023-43869/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-19319](https://insights.sbomify.com/CVE-2020-19319/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8978 is a high-severity vulnerability in Dlink Dir-619l Firmware, published on 14 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8978 exists.

Affected product: Dlink Dir-619l Firmware. 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-8978/ (Markdown: https://insights.sbomify.com/CVE-2025-8978/index.md)
```

## Sources

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

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