CVE-2025-10385
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 · uneditedA vulnerability has been found in Mercury KM08-708H GiGA WiFi Wave2 1.1. Affected by this issue is the function sub_450B2C of the file /goform/mcr_setSysAdm. The manipulation of the argument ChgUserId leads to buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
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 · moderate confidenceBuffer overflow vulnerability in Mercury KM08-708H GiGA WiFi Wave2 router's web management interface. The sub_450B2C function in /goform/mcr_setSysAdm processes the ChgUserId parameter without proper bounds checking, allowing remote attackers to overflow a buffer by providing an overly long user ID string. The public disclosure of the exploit increases exploitation likelihood.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 device model and firmware versionAccess the router's web management interface and check the system status or device info page for the exact model number (KM08-708H GiGA WiFi Wave2) and firmware version. Alternatively, check the label on the device itself or use SNMP queries if available.Affected if The device is a Mercury KM08-708H GiGA WiFi Wave2 router and the firmware version cannot be confirmed as patched (no patch version information available).
-
Verify web management interface is enabledAttempt to access the router's web interface via HTTP/HTTPS on the default management port (typically 80 or 443). Check router configuration for remote management settings.Affected if The web management interface is accessible, particularly from untrusted networks.
-
Confirm the vulnerable endpoint existsSend a request to the /goform/mcr_setSysAdm endpoint. This can be done by examining the router's firmware (if accessible) or by testing with a benign request. Look for the ChgUserId parameter processing functionality.Affected if The /goform/mcr_setSysAdm endpoint handles the ChgUserId parameter without proper length validation.
-
Check for exposure to untrusted networksReview the router's access control settings to determine if the web management interface is reachable from the WAN/Internet or only from the LAN/Trusted networks.Affected if The admin interface is exposed to untrusted networks or the Internet.
You are affected if you are using a Mercury KM08-708H GiGA WiFi Wave2 router with the web management interface accessible, particularly from untrusted networks, and the /goform/mcr_setSysAdm endpoint with ChgUserId parameter is present without known patched firmware.
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 vendor firmware update if available; otherwise, disable remote web management access, restrict admin interface to trusted networks only, or consider replacing the device with a currently supported model.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10385 — 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-10385 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