dbcve.org
InjectionWeakness · CWE-74

CVE-2025-2726

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, which was classified as critical, has been found in H3C Magic NX15, Magic NX30 Pro, Magic NX400, Magic R3010 and Magic BE18000 up to V100R014. Affected by this issue is some unknown functionality of the file /api/esps of the component HTTP POST Request Handler. The manipulation leads to command injection. Access to the local network is required for this attack. 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 the HTTP POST request handler for /api/esps on H3C Magic routers (NX15, NX30 Pro, NX400, R3010, BE18000) up to V100R014. An attacker with local network access can inject arbitrary commands through manipulated POST requests to this endpoint.

MitigationUpgrade the affected H3C Magic router firmware to a version beyond V100R014 as recommended by the vendor. Restrict local network access to trusted users as a 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
    Check the device label or web interface to confirm the exact H3C Magic model (NX15, NX30 Pro, NX400, R3010, or BE18000).
    Affected if Router is one of the listed H3C Magic models.
  2. Check firmware version
    Access the router web administration interface (typically at 192.168.1.1) and navigate to the Status or System Information page to view the firmware version. Alternatively, check the version banner in the web interface footer or system settings.
    Affected if Firmware version is V100R014 or earlier.
  3. Confirm endpoint accessibility
    From a device on the local network, verify the router responds to HTTP requests. Attempt to reach the /api/esps endpoint using a tool like curl: curl -X POST http://<router-ip>/api/esps -d "test"
    Affected if The /api/esps endpoint is reachable from the local network.
  4. Verify POST handler exists
    Send a crafted POST request to /api/esps and observe if the router processes it. A vulnerable router will accept and process POST data at this endpoint.
    Affected if The router accepts POST requests to /api/esps without authentication errors.

The environment is affected if the router is an H3C Magic model (NX15, NX30 Pro, NX400, R3010, BE18000) running firmware V100R014 or earlier, and the /api/esps endpoint is accessible from the local 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 the affected H3C Magic router firmware to a version beyond V100R014 as recommended by the vendor. Restrict local network access to trusted users as a compensating control.

Recommended fix Moderate confidence

Any firmware version newer than V100R014 (check H3C support site for latest available release)

  1. 1. Identify the exact model number of your H3C Magic router (NX15, NX30 Pro, NX400, R3010, or BE18000)
  2. 2. Access the H3C official support website at www.h3c.com or zhiliao.h3c.com
  3. 3. Navigate to the download/support section for your specific router model
  4. 4. Download the latest firmware version that is newer than V100R014
  5. 5. Access the router's web administration interface via a browser on the local network
  6. 6. Navigate to the firmware upgrade or system settings section
  7. 7. Upload and apply the new firmware version
  8. 8. After the upgrade completes, verify the router is functioning properly
Caveat Firmware upgrades may reset some configuration settings; 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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