VulnerabilityPublished 28 Oct 2025Updated 29 Oct 2025

CVE-2025-61128: WAVLINK QUANTUM D3G/WL-WN530HG3 firmware M30HG3_V240730 · Stack-based Buffer Overflow

Source CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediately identify and inventory all WAVLINK QUANTUM D3G/WL-WN530HG3 and other potentially affected models within the network. 2. Isolate vulnerable devices from critical network segments and restrict management interface access to trusted IP addresses only. 3. Implement network-level protections such as Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) to detect and block malicious POST requests targeting login.cgi with suspicious referrer headers. 4. Monitor network traffic and device logs for unusual POST requests or signs of exploitation attempts. 5. Disable remote management interfaces if not strictly necessary, or restrict them via VPN or secure tunnels. 6. Engage with WAVLINK support or vendors to obtain firmware updates or patches as soon as they become available. 7. Consider replacing vulnerable devices with models from vendors with a stronger security track record if immediate patching is not feasible. 8. Educate IT staff on the vulnerability details and ensure incident response plans include steps for potential exploitation scenarios. 9. Apply network segmentation to limit the impact of compromised devices on broader organizational infrastructure.

Description

Stack-based buffer overflow vulnerability in WAVLINK QUANTUM D3G/WL-WN530HG3 firmware M30HG3_V240730, and possibly other wavlink models allows attackers to execute arbitrary code via crafted referrer value POST to login.cgi.

Impact

For European organizations, the impact of CVE-2025-61128 can be severe. Compromise of WAVLINK routers could lead to unauthorized remote code execution, resulting in loss of confidentiality through interception of network traffic, disruption of availability by causing device crashes or network outages, and potential lateral movement within corporate networks. Critical infrastructure sectors such as finance, healthcare, and government agencies relying on these devices for secure connectivity could face operational disruptions and data breaches. The lack of authentication and user interaction requirements lowers the barrier for exploitation, increasing the risk of widespread attacks. Additionally, the vulnerability could be leveraged for launching further attacks such as man-in-the-middle, data exfiltration, or establishing persistent footholds. The absence of patches means organizations must rely on network-level mitigations and monitoring until firmware updates are available. The threat is particularly relevant for small and medium enterprises and remote offices that commonly deploy consumer-grade routers like WAVLINK devices due to cost considerations.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gist.github.com/shinobu-alpha/6dd5ad7f83c16360f6564db0bc121e99 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 5 Nov 2025, 02:16 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats