dbcve.org
InjectionWeakness · CWE-74

CVE-2025-3541

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, which was classified as critical, has been found in H3C Magic NX15, Magic NX30 Pro, Magic NX400 and Magic R3010 up to V100R014. Affected by this issue is the function FCGI_WizardProtoProcess of the file /api/wizard/getSpecs of the component HTTP POST Request Handler. The manipulation leads to command injection. The attack needs to 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

A command injection vulnerability exists in H3C Magic NX15, NX30 Pro, NX400, and R3010 routers up to V100R014. The flaw is in the FCGI_WizardProtoProcess function within the /api/wizard/getSpecs HTTP POST endpoint, allowing an attacker on the local network to execute arbitrary OS commands.

MitigationUpgrade H3C Magic router firmware to a version beyond V100R014 as recommended by the vendor. If no patched firmware is available, restrict network access to the affected devices and disable the wizard API endpoint if possible.

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 the router web interface or check the device label/SSH banner to confirm the exact model (NX15, NX30 Pro, NX400, or R3010)
    Affected if model is not one of NX15, NX30 Pro, NX400, or R3010 (not affected)
  2. Check firmware version
    Log into the router admin panel and locate the firmware version in system settings or run 'cat /proc/version' via telnet/SSH if available; compare your version to V100R014
    Affected if firmware version is V100R014 or lower (vulnerable)
  3. Verify wizard API accessibility
    Send a POST request to http://[router-ip]/api/wizard/getSpecs with any payload (e.g., {'test':'1'}) and observe if the endpoint responds
    Affected if endpoint returns a valid HTTP response (wizard API is exposed)
  4. Assess local network exposure
    Determine if the router management interface is reachable from untrusted network segments or if the device has default credentials that could allow local network attackers to access the admin panel
    Affected if router is accessible from network segments beyond the trusted admin workstation

You are affected if your router is an H3C Magic NX15, NX30 Pro, NX400, or R3010 model running firmware V100R014 or lower, with the wizard API endpoint exposed to untrusted network segments.

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 a version beyond V100R014 as recommended by the vendor. If no patched firmware is available, restrict network access to the affected devices and disable the wizard API endpoint if possible.

Recommended fix High confidence

Any firmware version newer than V100R014 (check H3C official downloads for the specific latest version number)

  1. 1. Identify the current firmware version of the H3C Magic device (NX15, NX30 Pro, NX400, or R3010) by accessing the router's web interface or administrative console
  2. 2. Navigate to the H3C official support website (www.h3c.com or zhiliao.h3c.com)
  3. 3. Locate the firmware download section for your specific device model
  4. 4. Download the latest firmware version that is newer than V100R014
  5. 5. Access the router's administration panel and navigate to the firmware upgrade section
  6. 6. Upload and apply the new firmware version, following the on-screen instructions
  7. 7. After the upgrade completes, verify the new firmware version is installed
  8. 8. Restart the device to ensure all services load with the updated firmware
Caveat Review H3C release notes for any configuration or feature changes between versions; backup current configuration before upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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