What is the CVSS score of CVE-2025-6291?

CVE-2025-6291 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Dir 825 Firmware are affected by CVE-2025-6291?

A critical stack-based buffer overflow vulnerability affects D-Link DIR-825 routers (model 2.03) that are no longer supported by the vendor, with public exploits already available.

Is there a public PoC exploit available for CVE-2025-6291?

Yes, a public proof-of-concept exploit is available for CVE-2025-6291. Prioritise patching immediately. EPSS: 0.2%.

How to fix or mitigate CVE-2025-6291?

Within 24 hours: Inventory all D-Link DIR-825 2.03 devices in production and isolate or disable any non-critical units; document business justification for retained devices. Within 7 days: Implement network segmentation to restrict direct internet access to affected devices and deploy WAF/IPS rules blocking known exploit patterns. Within 30 days: Develop and execute replacement plan for end-of-life equipment with supported alternatives, or decommission devices if operationally feasible.

Dir 825 Firmware CVE-2025-6291

EUVD-2025-28712 HIGH

Buffer Overflow (CWE-119)

2025-06-20 cna@vuldb.com

RCE Buffer Overflow D-Link Dir 825 Firmware

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

EUVD ID Assigned

Mar 15, 2026 - 00:19 euvd

EUVD-2025-28712

Analysis Generated

Mar 15, 2026 - 00:19 vuln.today

PoC Detected

Jun 26, 2025 - 17:00 vuln.today

Public exploit code

CVE Published

Jun 20, 2025 - 01:15 nvd

HIGH 8.8

DescriptionCVE.org

A vulnerability, which was classified as critical, was found in D-Link DIR-825 2.03. This affects the function do_file of the component HTTP POST Request Handler. The manipulation leads to stack-based buffer overflow. It is possible to initiate the attack remotely. 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.

AnalysisAI

CVE-2025-6291 is a critical stack-based buffer overflow vulnerability in D-Link DIR-825 firmware version 2.03, exploitable via HTTP POST requests to the do_file function. An authenticated attacker can achieve complete system compromise (confidentiality, integrity, and availability violations) remotely without user interaction. Public exploit code exists and the affected product is end-of-life with no vendor support, elevating real-world risk despite authentication requirement.

Technical ContextAI

The vulnerability exists in the HTTP POST Request Handler component of D-Link DIR-825 wireless router firmware (CPE: cpe:2.3:h:d-link:dir-825:-:*:*:*:*:*:*:* with firmware 2.03). The root cause is CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), specifically a stack-based buffer overflow in the do_file function. This function fails to properly validate the length of user-supplied input before copying it to a fixed-size stack buffer during HTTP POST parameter processing. The vulnerability allows attackers to overwrite return addresses and execute arbitrary code with device privileges.

RemediationAI

No vendor patches are available for this end-of-life product. Recommended mitigation: (1) IMMEDIATE: Disable HTTP POST requests at firewall level or disable remote management if not required; (2) Apply strong, unique credentials to router administration interface and change defaults; (3) Network isolation: restrict access to administrative interfaces to trusted networks only; (4) CRITICAL: Deploy replacement hardware with actively maintained firmware; (5) Implement network segmentation to limit router compromise impact; (6) Monitor router logs for suspicious POST requests or failed authentication attempts; (7) If continued operation is unavoidable, disable HTTP management and use only HTTPS with certificate pinning from trusted networks.