The argument name 'my2P4key' in the 'wan.repeater.set' endpoint is your most important diagnostic clue. The 'my' prefix and phonetic substitution ('2' for 'to', '4' for 'for') are hallmarks of prototyping code that shipped — developers use this convention when rapidly testing internally, intending to rename before release, then never do. If this is what happened with NX15 firmware, you're not looking at an isolated coding error. You're looking at evidence that H3C's development process has no gate between 'prototyping complete' and 'firmware shipped.' That matters because other non-standard argument names almost certainly exist in other NX15 API endpoints, each potentially representing additional command injection surface. Static analysis of other /api/esps* endpoints should be your immediate priority — if they share similar naming conventions, the authentication failure is likely systemic across the entire API layer, not isolated to this function. The 'wan.repeater.set' context places this at the network perimeter. A command injection here doesn't just give you the router — it gives you a transparent bridge position in the traffic path, effectively a man-in-the-middle position for every device downstream. The public Metasploit module changes the threat model: consumer NX15 deployments in SMB and residential environments rarely receive firmware updates within the first year of a CVE. The actual exposure window is measured in years, not weeks. Regardless of whether the underlying issue is a CLI-to-HTTP scaffold that never received authentication retrofit or a third-party web component with delegated access control, the structural failure is the same — this API layer was never designed to be exposed. Assume it's exploitable without credentials until proven otherwise, and prioritize network segmentation around any NX15 device at the WAN edge.
CVE-2026-18902
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 · uneditedA vulnerability was detected in H3C NX15 V100R017. Affected by this vulnerability is the function esps.wan.repeater.set/repeaterproc of the file /api/esps. Performing a manipulation of the argument my2P4key results in command injection. Remote exploitation of the attack is possible. The exploit is now public and may 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 analysisUntrusted input crosses into a downstream interpreter — SQL, a shell, an HTML page, an LDAP query — without being kept separate from the commands around it, so the attacker's data is read as instructions. This is the parent class behind SQL injection, cross-site scripting, and command injection alike. The durable fix is the same everywhere: keep data and code apart at every boundary, using parameterisation or context-aware encoding rather than building interpreted strings by concatenation.
General guidance for the injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $1,950. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-18902 — 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 sourcesThe argument name 'my2P4key' in the 'wan.repeater.set' endpoint is your most important diagnostic clue. The 'my' prefix and phonetic substitution ('2' for 'to', '4' for 'for') are hallmarks of prototyping code that shipped — developers use this convention when rapidly testing internally, intending to rename before release, then never do. If this is what happened with NX15 firmware, you're not looking at an isolated coding error. You're looking at evidence that H3C's development process has no gate between 'prototyping complete' and 'firmware shipped.' That matters because other non-standard argument names almost certainly exist in other NX15 API endpoints, each potentially representing additional command injection surface. Static analysis of other /api/esps* endpoints should be your immediate priority — if they share similar naming conventions, the authentication failure is likely systemic across the entire API layer, not isolated to this function. The 'wan.repeater.set' context places this at the network perimeter. A command injection here doesn't just give you the router — it gives you a transparent bridge position in the traffic path, effectively a man-in-the-middle position for every device downstream. The public Metasploit module changes the threat model: consumer NX15 deployments in SMB and residential environments rarely receive firmware updates within the first year of a CVE. The actual exposure window is measured in years, not weeks. Regardless of whether the underlying issue is a CLI-to-HTTP scaffold that never received authentication retrofit or a third-party web component with delegated access control, the structural failure is the same — this API layer was never designed to be exposed. Assume it's exploitable without credentials until proven otherwise, and prioritize network segmentation around any NX15 device at the WAN edge.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-18902 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
- 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