CVE-2025-6091
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 was found in H3C GR-3000AX V100R007L50. It has been classified as critical. Affected is the function UpdateWanParamsMulti/UpdateIpv6Params of the file /routing/goform/aspForm. The manipulation of the argument param leads to buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor confirms the existence of this issue. Because they assess the risk as low, they do not have immediate plans for remediation.
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 buffer overflow vulnerability exists in the H3C GR-3000AX router firmware (V100R007L50) within the UpdateWanParamsMulti/UpdateIpv6Params functions of the web interface (/routing/goform/aspForm). The overflow occurs via the 'param' argument and can be exploited remotely with publicly available exploit code, achieving high severity (CVSS 8.8).
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 the router modelAccess the router's web interface or CLI and retrieve the device model information. This is typically visible on the login page, status page, or obtainable via 'show version' command in CLI.Affected if The device is not an H3C GR-3000AX router
-
Check the firmware versionNavigate to the router's administration interface and locate the firmware version information, usually found under System Settings, Device Info, or Status. In CLI, use 'show version' or similar command.Affected if The firmware version is V100R007L50 (exact match)
-
Verify the web interface is accessibleAttempt to access the router's web interface at the default IP (commonly 192.168.0.1 or 192.168.1.1) and confirm the /routing/goform/aspForm endpoint responds.Affected if The web interface and the /routing/goform/aspForm endpoint are reachable from the network being assessed
-
Confirm the vulnerable functions existSend a request to /routing/goform/aspForm and observe if the UpdateWanParamsMulti or UpdateIpv6Params functions are present and accept the 'param' argument.Affected if The endpoint responds and accepts the 'param' parameter without proper authentication or validation
A user is affected if they are running an H3C GR-3000AX router with firmware version V100R007L50 and the web interface at /routing/goform/aspForm is accessible on their network.
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 dataImplement network segmentation to isolate the router from untrusted networks, restrict web interface access to trusted IPs only, and monitor for exploitation attempts until vendor firmware is available.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6091 — 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-6091 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