dbcve.org
InjectionWeakness · CWE-74

CVE-2025-2732

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. It has been rated as critical. Affected by this issue is some unknown functionality of the file /api/wizard/getWifiNeighbour of the component HTTP POST Request Handler. The manipulation leads to command injection. The attack needs to be initiated 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's HTTP POST Request Handler for the /api/wizard/getWifiNeighbour endpoint allows unauthenticated attackers on the local network to execute arbitrary commands via manipulated requests.

MitigationUpgrade affected H3C Magic router firmware (NX15, NX30 Pro, NX400, R3010, BE18000) from V100R014 to a patched version. If upgrade unavailable, restrict network access to the management interface.

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
    Access router admin interface or check device label/marketing to confirm the model is one of: NX15, NX30 Pro, NX400, R3010, or BE18000
    Affected if Router model is any of the listed H3C Magic models
  2. Check firmware version
    Log into router admin panel (typically at 192.168.1.1 or 192.168.0.1), navigate to System Settings or Status page, and locate the firmware version field
    Affected if Firmware version is V100R014 or earlier (unpatched)
  3. Verify endpoint accessibility
    From a device on the local network, attempt to access http://<router-ip>/api/wizard/getWifiNeighbour via POST request using a tool like curl or Burp Suite
    Affected if Endpoint responds with any HTTP status (indicating it is exposed and potentially vulnerable)
  4. Check management interface exposure
    Review router network settings to determine if the admin interface is accessible from WAN/external networks, or scan external IP for open HTTP/HTTPS ports to router admin
    Affected if Management interface is exposed to WAN or untrusted networks

User is affected if they have an H3C Magic router (NX15, NX30 Pro, NX400, R3010, or BE18000) running firmware V100R014 or earlier with the /api/wizard/getWifiNeighbour endpoint accessible from an untrusted network.

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 affected H3C Magic router firmware (NX15, NX30 Pro, NX400, R3010, BE18000) from V100R014 to a patched version. If upgrade unavailable, restrict network access to the management interface.

Recommended fix Moderate confidence

V100R015 or later (next release after V100R014)

  1. 1. Identify the current firmware version of the H3C Magic device by accessing the web management interface or checking the device label
  2. 2. Download the latest firmware version from the official H3C support website (www.h3c.com or zhiliao.h3c.com)
  3. 3. Access the device's administration panel and navigate to the firmware upgrade section
  4. 4. Upload and install the latest firmware version to remediate the command injection vulnerability in /api/wizard/getWifiNeighbour
  5. 5. After upgrade, verify the device is functioning correctly and the vulnerability is resolved
Caveat Review release notes for any configuration changes or feature modifications in the new firmware version

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 / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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