dbcve.org
InjectionWeakness · CWE-74

CVE-2025-2729

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 was found in H3C Magic NX15, Magic NX30 Pro, Magic NX400, Magic R3010 and Magic BE18000 up to V100R014 and classified as critical. This issue affects some unknown processing of the file /api/wizard/networkSetup of the component HTTP POST Request Handler. The manipulation leads to command injection. The attack can only be done within the local network. The exploit has been disclosed to the public and may be used. 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

Command injection vulnerability in H3C Magic router firmware allows remote attackers within the local network to execute arbitrary commands via crafted POST requests to the /api/wizard/networkSetup endpoint. The issue affects multiple Magic model routers (NX15, NX30 Pro, NX400, R3010, BE18000) up to version V100R014.

MitigationUpgrade H3C Magic router firmware to the latest version beyond V100R014. Restrict local network access to administrative interfaces and disable the wizard/setup endpoints if not in use.

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 router model
    Check the label on the router or log into the web admin interface to confirm the exact model (NX15, NX30 Pro, NX400, R3010, or BE18000).
    Affected if Model is one of NX15, NX30 Pro, NX400, R3010, or BE18000.
  2. Check firmware version
    Access the router web admin interface, navigate to the Status or System settings page, and record the firmware version displayed. Compare it to V100R014.
    Affected if Firmware version is V100R014 or any version below V100R014.
  3. Verify networkSetup API endpoint exists
    From a device on the local network, send a POST request to http://<router-ip>/api/wizard/networkSetup using a tool like curl. Observe if the endpoint responds (even with an error).
    Affected if The /api/wizard/networkSetup endpoint is reachable and responds to requests.
  4. Confirm administrative interface accessibility
    Confirm the router web admin interface (port 80 or 443) is accessible from the local network segment where the attack would originate.
    Affected if The administrative interface is accessible from the local network without restriction.

If the router model is an affected H3C Magic variant and the firmware version is V100R014 or lower, and the /api/wizard/networkSetup endpoint is accessible from the local network, the environment is affected by this vulnerability.

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

Upgrade H3C Magic router firmware to the latest version beyond V100R014. Restrict local network access to administrative interfaces and disable the wizard/setup endpoints if not in use.

Recommended fix Moderate confidence

Any firmware version newer than V100R014 (contact H3C for specific fixed release number)

  1. 1. Identify the current firmware version of the H3C Magic device (NX15, NX30 Pro, NX400, R3010, or BE18000) by accessing the web administration interface or checking the device label
  2. 2. Navigate to the H3C official support website (www.h3c.com or zhiliao.h3c.com) and locate the firmware download section for your specific device model
  3. 3. Download the latest available firmware version for your device. The vulnerability affects versions up to and including V100R014, so any version newer than V100R014 should contain the fix
  4. 4. Access the device's administration interface and locate the firmware upgrade or system maintenance section
  5. 5. Upload and apply the new firmware version, ensuring stable power during the upgrade process
  6. 6. After the device restarts, verify the new firmware version is installed and confirm the /api/wizard/networkSetup endpoint is no longer vulnerable to command injection
  7. 7. If remote management was enabled, ensure it is disabled or properly secured since this vulnerability requires local network access
Caveat Review H3C release notes for your specific model for any configuration or feature changes between versions

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

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-2729 — 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-2729 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