dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-44635

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
There are multiple unauthorized remote command execution vulnerabilities in the H3C ER2200G2, ERG2-450W, ERG2-1200W, ERG2-1350W, NR1200W series routers before ERG2AW-MNW100-R1117; H3C ER3100G2, ER3200G2, ER3260G2, ER5100G2, ER5200G2, ER6300G2, ER8300G2, ER8300G2-X series routers before ERHMG2-MNW100-R1126; GR3200, GR5200, GR8300 and other series routers before MiniGR1B0V100R018L50; GR-1800AX before MiniGRW1B0V100R009L50; GR-3000AX before SWBRW1A0V100R007L50; and GR-5400AX before SWBRW1B0V100R009L50. Attackers can bypass authentication by including specially crafted text in the request URL or message header, and then inject arbitrary malicious commands into some fields related to ACL access control list and user group functions and execute to obtain the highest ROOT privileges of remote devices, thereby completely taking over the remote target devices.

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 confidence

This is a pre-authentication command injection vulnerability affecting multiple H3C router series. Attackers bypass authentication using specially crafted text in HTTP requests, then inject malicious commands into ACL and user group configuration fields, achieving root-level remote code execution and full device takeover.

MitigationApply vendor-supplied firmware updates to the latest patched versions (ERG2AW-MNW100-R1117, ERHMG2-MNW100-R1126, MiniGR1B0V100R018L50, MiniGRW1B0V100R009L50, SWBRW1A0V100R007L50, SWBRW1B0V100R009L50). If patching is not immediately possible, restrict administrative interface access to trusted networks or disable remote management via WAN.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify H3C router model
    Access the device administrative interface or check the device label/serial number to confirm the exact model (ERG2AW, ERHMG2, MiniGR1B0, MiniGRW1B0, SWBRW1A0, or SWBRW1B0)
    Affected if The device is an H3C router from one of these series and the firmware has not been updated to the patched versions (ERG2AW-MNW100-R1117, ERHMG2-MNW100-R1126, MiniGR1B0V100R018L50, MiniGRW1B0V100R009L50, SWBRW1A0V100R007L50, SWBRW1B0V100R009L50)
  2. Check current firmware version
    Log into the router web interface or CLI and locate the firmware/version information typically found under System Status, Device Info, or About sections
    Affected if The running firmware version is lower than the patched versions listed above (meaning the version number is older than R1117 for ERG2AW, R1126 for ERHMG2, R018L50 for MiniGR1B0, R009L50 for MiniGRW1B0/SWBRW1B0, or R007L50 for SWBRW1A0)
  3. Verify remote management exposure
    Check the router configuration for remote management settings, typically under System Tools > Remote Management, Security settings, or WAN Access settings, to determine if the HTTP administrative interface is accessible from WAN/external IP addresses
    Affected if Remote management over HTTP is enabled and the administrative interface is accessible from untrusted networks or the WAN interface
  4. Inspect ACL configuration for unauthorized rules
    Access the router ACL (Access Control List) configuration section and review all rules for any unexpected or suspicious entries, particularly those containing unusual command strings, IP addresses, or patterns not configured by your organization
    Affected if ACL rules contain unexpected entries with command-like syntax or configurations that were not intentionally created by the administrator
  5. Inspect user group configuration for modifications
    Navigate to the user group or administrator account settings and verify that all accounts and group memberships match known, intended configurations
    Affected if There are additional user accounts, modified privilege levels, or group assignments that were not created by an authorized administrator

A user is affected if they run an unpatched H3C router from the affected series with remote management exposed to untrusted networks, or if their device configuration shows unexpected ACL or user group modifications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates to the latest patched versions (ERG2AW-MNW100-R1117, ERHMG2-MNW100-R1126, MiniGR1B0V100R018L50, MiniGRW1B0V100R009L50, SWBRW1A0V100R007L50, SWBRW1B0V100R009L50). If patching is not immediately possible, restrict administrative interface access to trusted networks or disable remote management via WAN.

Recommended fix Moderate confidence

ERG2AW-MNW100-R1117 (for ER2200G2, ERG2-450W, ERG2-1200W, ERG2-1350W, NR1200W); ERHMG2-MNW100-R1126 (for ER3100G2, ER3200G2, ER3260G2, ER5100G2, ER5200G2, ER6300G2, ER8300G2, ER8300G2-X); MiniGR1B0V100R018L50 (for GR3200, GR5200, GR8300); MiniGRW1B0V100R009L50 (for GR-1800AX); SWBRW1A0V100R007L50 (f

  1. 1. Identify the exact H3C router model from the affected series (ER2200G2, ERG2-450W, ERG2-1200W, ERG2-1350W, NR1200W, ER3100G2, ER3200G2, ER3260G2, ER5100G2, ER5200G2, ER6300G2, ER8300G2, ER8300G2-X, GR3200, GR5200, GR8300, GR-1800AX, GR-3000AX, GR-5400AX).
  2. 2. Access the router's web management interface or CLI console.
  3. 3. Navigate to the firmware upgrade or system maintenance section.
  4. 4. Download the appropriate firmware version from the official H3C support website (www.h3c.com).
  5. 5. Upload and apply the firmware upgrade to the router.
  6. 6. After upgrade, verify the router is functioning normally and confirm the firmware version matches the fixed release.
Caveat Firmware upgrades carry inherent risks; ensure power stability during upload and verify compatibility with existing network configurations before deploying.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-44635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-44635 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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