dbcve.org
InjectionWeakness · CWE-74

CVE-2025-2728

HIGH · 8.0 CVSS v3.1 Published 2025-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
A vulnerability has been found in H3C Magic NX30 Pro and Magic NX400 up to V100R014 and classified as critical. This vulnerability affects unknown code of the file /api/wizard/getNetworkConf. The manipulation leads to command injection. The attack needs to be approached within the local network. It is recommended to upgrade the affected component.

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

A command injection vulnerability exists in the /api/wizard/getNetworkConf API endpoint of H3C Magic NX30 Pro and Magic NX400 routers running firmware up to V100R014. An attacker with local network access can manipulate input to this endpoint to execute arbitrary commands on the underlying operating system.

MitigationUpgrade the H3C Magic NX30 Pro and Magic NX400 routers to firmware version V100R014 or later to address the command injection vulnerability in the /api/wizard/getNetworkConf endpoint.

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 checks

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

  1. Identify the router model
    Access the router admin interface or check the device label to confirm the model is H3C Magic NX30 Pro or Magic NX400
    Affected if The device is not an H3C Magic NX30 Pro or Magic NX400 model
  2. Check the installed firmware version
    Log into the router web interface and navigate to Administration > Firmware Upgrade, or use the command 'show version' via telnet/SSH if available, to determine the current firmware version
    Affected if The firmware version is V100R014 or any version earlier than V100R014
  3. Verify the vulnerable API endpoint is present
    Attempt to access or probe the endpoint http://<router-ip>/api/wizard/getNetworkConf using a GET or POST request from within the local network
    Affected if The endpoint responds and accepts input without authentication or with default credentials
  4. Confirm command injection is possible
    Send a crafted request to /api/wizard/getNetworkConf with command injection characters in the input parameters (for example, adding ';ls' or '|ls' to a parameter) and observe if the router returns unexpected output
    Affected if The API endpoint executes injected commands and returns system output

A user is affected if they have an H3C Magic NX30 Pro or Magic NX400 router running firmware V100R014 or earlier, with the /api/wizard/getNetworkConf endpoint accessible and vulnerable to command injection.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the H3C Magic NX30 Pro and Magic NX400 routers to firmware version V100R014 or later to address the command injection vulnerability in the /api/wizard/getNetworkConf endpoint.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2728 — 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-2728 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