CVE-2025-61128
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStack-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stack-based buffer overflow vulnerability exists in the login.cgi endpoint of WAVLINK QUANTUM D3G and WL-WN530HG3 devices (firmware M30HG3_V240730) where an attacker can send a crafted referrer value via POST request that overflows a stack-allocated buffer, enabling arbitrary code execution with the privileges of the affected service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WAVLINK router modelAccess the router admin interface or check the device label/box for model number. Look for QUANTUM D3G, WL-WN530HG3, or M30HG3 designations.Affected if Device is a WAVLINK router matching the QUANTUM D3G, WL-WN530HG3, or M30HG3 model families.
-
Check firmware versionLog into the router admin panel and navigate to System Settings or Status page to view the firmware version. Alternatively, check the vendor support page for your specific model.Affected if Firmware version is M30HG3_V240730 or earlier, or matches any affected model without an available security patch.
-
Verify login.cgi endpoint accessibilityAttempt to access the router web interface at the /login.cgi path (e.g., http://192.168.1.1/login.cgi) using a web browser or curl command.Affected if The login.cgi endpoint is reachable from an untrusted network without IP or network-based access restrictions.
-
Confirm Referrer header handlingSend a POST request to login.cgi with an unusually long Referrer header value using a tool like Burp Suite or curl. Observe if the device responds unexpectedly or crashes.Affected if The device accepts and processes the Referrer header without length validation, indicating the vulnerability is present.
A user is affected if they own a WAVLINK QUANTUM D3G, WL-WN530HG3, or M30HG3 router running firmware version M30HG3_V240730 or earlier, and the router administrative interface is accessible without proper network restrictions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply available firmware updates from WAVLINK; if no update exists, restrict access to the device's web management interface to trusted networks only or deploy WAF rules to filter abnormally long referrer headers until a patch is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61128 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61128 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data