dbcve.org
CWE-640Weakness · CWE-640

CVE-2026-15479

HIGH · 7.3 CVSS v3.1 Published 2026-07-12
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
Remotely reachable No privileges Zero-click 6 weeks old

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 NX15 V100R017. Affected by this vulnerability is the function change_passwd of the file /api/login/modify of the component Administrator Password Modification Endpoint. The manipulation of the argument newPass results in weak password recovery. The attack may be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure.

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 · moderate confidence

The H3C NX15 V100R017 router has a weak password recovery mechanism in the /api/login/modify endpoint's change_passwd function. The vulnerability allows remote attackers to potentially modify administrator passwords without proper authentication or with insufficient validation, leading to unauthorized administrative access.

MitigationRestrict access to the password modification endpoint with proper authentication checks, implement strong password policy enforcement, validate all input parameters server-side, and consider rate-limiting or IP-based restrictions on administrative endpoints. Update to vendor patch when available.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 the device model and firmware version
    Access the router web interface (typically 192.168.1.1) and navigate to Status or System Info page to view the firmware version. Alternatively, use SNMP (snmpwalk on OID 1.3.6.1.2.1.1) or check the admin page footer for version information.
    Affected if The device is an H3C NX15 running firmware version V100R017 (or any version within the same release branch before patching)
  2. Confirm the router's management interface is accessible remotely
    Check the router's administrative settings page for remote management options. Look for 'Remote Management' or 'Web Management' settings and verify if remote IP addresses are allowed or if WAN access is enabled.
    Affected if Remote administrative access is enabled, allowing the vulnerable endpoint to be reached from outside the local network
  3. Test access to the password modification endpoint
    Attempt to access the /api/login/modify endpoint via HTTP/HTTPS from a remote location. Use a tool like curl to send a request to http://[router-ip]/api/login/modify and observe the response.
    Affected if The endpoint responds without requiring authentication or returns a valid-looking response rather than an authentication error
  4. Inspect HTTP response behavior for the change_passwd function
    Send a crafted password change request (even with invalid credentials) to /api/login/modify and examine whether the server processes the request or immediately rejects it with an authentication error code (such as 401 or 403).
    Affected if The server accepts the request and returns a success or partial response instead of rejecting it with proper authentication failure

You are affected if you are running an H3C NX15 V100R017 router with remote management enabled and the /api/login/modify endpoint accepts unauthenticated or improperly validated password change requests.

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

Restrict access to the password modification endpoint with proper authentication checks, implement strong password policy enforcement, validate all input parameters server-side, and consider rate-limiting or IP-based restrictions on administrative endpoints. Update to vendor patch when available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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