dbcve.org
InjectionWeakness · CWE-74

CVE-2025-3544

HIGH · 8.0 CVSS v3.1 Published 2025-04-14
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 the function FCGI_CheckStringIfContainsSemicolon of the file /api/wizard/getCapabilityWeb of the component HTTP POST Request Handler. The manipulation leads to command injection. Access to the local network is required for this attack to succeed. 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 the HTTP POST request handler for the /api/wizard/getCapabilityWeb endpoint in H3C Magic routers (models NX15, NX30 Pro, NX400, R3010, BE1800) up to V100R014. The FCGI_CheckStringIfContainsSemicolon function fails to properly sanitize input, allowing authenticated attackers with local network access to execute arbitrary system commands through the web interface.

MitigationUpgrade the H3C Magic router firmware to a version beyond V100R014 that contains the security patch. Until then, restrict network access to the device management interface and monitor for indicators of compromise.

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 admin web interface or check the device label to confirm the exact model number (NX15, NX30 Pro, NX400, R3010, or BE1800)
    Affected if The model is one of NX15, NX30 Pro, NX400, R3010, or BE1800
  2. Check firmware version
    Log into the router web management interface and navigate to System Settings or Status page to view the firmware version. Compare it to V100R014.
    Affected if Firmware version is V100R014 or lower (any version up to and including V100R014)
  3. Verify web interface accessibility
    Check if the router HTTP/HTTPS management interface is accessible from the network. Attempt to access the device from an external IP or confirm network exposure settings.
    Affected if The web management interface is exposed beyond the local network (e.g., accessible via WAN)
  4. Confirm vulnerable endpoint exists
    Send a POST request to http://<router-ip>/api/wizard/getCapabilityWeb and observe if the endpoint responds. This requires authentication to the web interface first.
    Affected if The endpoint returns any response (even an error) indicating it exists and is reachable

The device is affected if it is an H3C Magic model (NX15, NX30 Pro, NX400, R3010, or BE1800) running firmware version V100R014 or lower, AND the web management interface is accessible to untrusted networks.

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 the H3C Magic router firmware to a version beyond V100R014 that contains the security patch. Until then, restrict network access to the device management interface and monitor for indicators of compromise.

Recommended fix Moderate confidence

Firmware version newer than V100R014 (contact H3C support for exact version number)

  1. 1. Identify the current firmware version of the H3C Magic device by accessing the web management interface or using the CLI command 'display version'
  2. 2. Check H3C's official support website (www.h3c.com or zhiliao.h3c.com) for the latest firmware version for your specific model (NX15, NX30 Pro, NX400, R3010, or BE18000)
  3. 3. Download the firmware version newer than V100R014 from H3C's official support portal
  4. 4. Access the device's web management interface and navigate to the firmware upgrade section (typically under System Tools > Firmware Upgrade)
  5. 5. Upload the new firmware file and initiate the upgrade process
  6. 6. Wait for the upgrade to complete and the device to reboot automatically
  7. 7. After reboot, verify the new firmware version is installed and confirm the vulnerability is patched
Caveat Review H3C release notes for any configuration or feature changes between versions; backup current device configuration before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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