InjectionWeakness · CWE-74

CVE-2025-3540

HIGH · 8.0 CVSS v3.1 Published 2025-04-13
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 classified as critical was found in H3C Magic NX15, Magic NX30 Pro, Magic NX400 and Magic R3010 up to V100R014. Affected by this vulnerability is the function FCGI_WizardProtoProcess of the file /api/wizard/getCapability of the component HTTP POST Request Handler. The manipulation leads to command injection. The attack can only 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 routers (NX15, NX30 Pro, NX400, R3010) in the FCGI_WizardProtoProcess function of /api/wizard/getCapability. The vulnerability allows injection of arbitrary OS commands via crafted HTTP POST requests. Exploitation is limited to local network attackers, but a public exploit exists.

MitigationUpgrade affected H3C Magic router firmware to a version beyond V100R014. Restrict network access to the router's management interface to trusted local users only as an interim compensating control.

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 panel or check device label to confirm model is NX15, NX30 Pro, NX400, or R3010
    Affected if Device is one of the four affected H3C Magic models
  2. Check firmware version
    Log into router web interface or check via CLI command, compare installed version to V100R014
    Affected if Firmware version is V100R014 or earlier (versions beyond V100R014 are patched)
  3. Assess management interface exposure
    Determine if router web interface is accessible from untrusted networks or directly from the internet
    Affected if Management interface is exposed beyond trusted local users only

Router is affected if it is an H3C Magic NX15, NX30 Pro, NX400, or R3010 running firmware V100R014 or earlier with the /api/wizard/getCapability endpoint reachable from the attacker's network location

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 affected H3C Magic router firmware to a version beyond V100R014. Restrict network access to the router's management interface to trusted local users only as an interim compensating control.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3540 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