CVE-2025-9938

D-Link Di-8400 Firmware buffer overflow

8.8 HIGHPublic exploitEPSS 1.55%

Published4 Sept 2025

Description

A weakness has been identified in D-Link DI-8400 16.07.26A1. The affected element is the function yyxz_dlink_asp of the file /yyxz.asp. This manipulation of the argument ID causes stack-based buffer overflow. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be exploited.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

D-Link Di-8400 Firmware16.07.26a1

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://github.com/ZZ2266/.github.io/tree/main/Dlink/DI-8400/yyxz.aspExploitThird Party Advisory
https://github.com/ZZ2266/.github.io/tree/main/Dlink/DI-8400/yyxz.asp#proof-of-concept-pocExploitThird Party Advisory
https://vuldb.com/?ctiid.322340Permissions RequiredVDB Entry
https://vuldb.com/?id.322340Third Party AdvisoryVDB Entry
https://vuldb.com/?submit.643446Third Party AdvisoryVDB Entry
https://www.dlink.com/Product

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-9938 being actively exploited?

CVE-2025-9938 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.55%.

How severe is CVE-2025-9938?

CVE-2025-9938 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 1.55% probability of exploitation.

Which products are affected by CVE-2025-9938?

Affected products include D-Link Di-8400 Firmware.

How do I fix CVE-2025-9938?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-9938 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.