← Back to Feed CACHED · 2026-05-17 09:42:19 · cache_key CVE-2025-29912
CVE-2026-34472 · CWE-200 · Disclosed 2026-03-30

Unauthenticated credential disclosure in the wizard interface in ZTE ZXHN H188A V6

ASSESSED — NOISGATE V0.5
Vendor
Reassessed
Verdict:
01 · The Real Story

This is a house key left under the router's welcome mat, but only for people already on the porch

CVE-2026-34472 is a pre-authentication information disclosure in the ZTE ZXHN H188A wizard flow affecting firmware V6.0.10P2_TE and V6.0.10P3N3_TE. An unauthenticated request can hit pre-login wizard handlers and pull credential-bearing data from the web interface, including WLAN material and PPPoE data; the public research says the leaked Wi-Fi password can also map to the default administrator password after uppercasing, which turns disclosure into effective admin bypass on validated devices.

The vendor baseline of HIGH is understandable in a lab because the bug is unauthenticated and can collapse straight into administrative access. In real enterprise operations, though, the deciding friction is attacker position: the published CVSS uses AV:A, meaning the attacker must already be on the local network or otherwise have reachability to the management plane, which sharply reduces exposed population versus true internet-scale pre-auth bugs.

"Serious on exposed branch CPE, but the adjacent-network prerequisite keeps this out of top-tier enterprise patch panic."
02 · The Attack Path

4 steps from start to impact.

STEP 01

Reach the router management plane with curl or any HTTP client

The attacker first needs HTTP reachability to the ZXHN H188A web UI. In the published scoring this is AV:A, so the normal path is same-LAN access, guest Wi-Fi access, branch-office foothold, or a misconfigured router exposing management externally.
Conditions required:
  • Target is a ZTE ZXHN H188A
  • Firmware is V6.0.10P2_TE or V6.0.10P3N3_TE
  • Attacker can reach the router web interface over the local network or exposed WAN management
Where this breaks in practice:
  • Most enterprise attackers do not begin on the same LAN as the branch router
  • Well-run environments block router management from guest VLANs and the internet
  • Many enterprises do not deploy this specific ISP/CPE model at scale
Detection/coverage: Standard vuln scanners may miss this unless they include the exact wizard endpoint logic; generic web scans usually only test login-protected paths.
STEP 02

Call the pre-login wizard handler from the public PoC logic

Per the researcher write-up, attacker-controlled _type and _tag parameters on root-path requests can route unauthenticated traffic into wizard handlers such as getPassword, wlan_get, and ppp_get. That bypasses the normal quick-setup gate and returns credential-bearing data without authentication.
Conditions required:
  • The root-path routing behavior matches the published vulnerable logic
  • Wizard handlers are reachable and not blocked by an upstream ACL
Where this breaks in practice:
  • Any upstream ACL, management-plane firewall, or reverse-proxy restriction breaks the chain
  • Vendor variations or ISP-customized builds may behave differently from the validated samples
Detection/coverage: Look for unauthenticated GET requests containing _type=tedataNotLoginData, _tag=wizard_lua.lua, and IF_ACTION=getPassword|wlan_get|ppp_get in proxy, firewall, or router HTTP logs.
STEP 03

Extract WLAN and PPPoE secrets with the researcher PoC

The public disclosure states the vulnerable handlers can return WLAN PSKs, SSIDs, and PPPoE usernames, and the advisory states default admin credentials may also be recoverable. On validated H188A devices, the leaked Wi-Fi password can become the admin password after uppercasing, which converts info leak into practical authentication bypass.
Conditions required:
  • Returned data includes credential material
  • Device still uses the documented default credential relationship
Where this breaks in practice:
  • If the admin password was changed away from the derived default, full panel takeover may stop at disclosure
  • Some environments care more about router admin compromise than PPPoE or Wi-Fi leakage, limiting blast radius
Detection/coverage: Network IDS can key off the distinctive query string and unusual pre-auth reads; host-based telemetry on CPE is typically poor.
STEP 04

Log in and change configuration using the disclosed credentials

With working admin credentials, the attacker can alter router settings, impact connected users, or pivot through trusted branch connectivity. Even without full admin reuse, PPPoE and wireless secrets are still sensitive and can expose adjacent access paths.
Conditions required:
  • Leaked credentials are valid for admin access or enable further network access
  • Management actions are permitted from the attacker's source network
Where this breaks in practice:
  • MFA is generally absent on this class of device, but source-IP restrictions or separate admin credentials can stop takeover
  • Impact is usually constrained to that router, that branch, or that home-office edge rather than the whole enterprise
Detection/coverage: Successful admin logins from unusual internal segments, sudden config changes, and PPPoE/WLAN modifications are the best practical signals.
03 · Intelligence Metadata

The supporting signals.

In-the-wild statusNo confirmed in-the-wild exploitation found in the sources reviewed, and not listed in CISA KEV.
Proof-of-concept availabilityPublic PoC and technical write-up exist from Mina Nageh Salalma / Monx Research via GitHub repo, public gist, and Full Disclosure advisory.
EPSS0.00829 (~0.829%), which is low and consistent with a niche, adjacency-bound router flaw rather than internet-scale mass exploitation.
KEV statusNot KEV-listed as of the reviewed CISA catalog.
CVSS vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N = easy to trigger once reachable, but reachability itself is the real brake because AV:A implies same network segment or equivalent management-plane access.
Affected versionsZTE ZXHN H188A firmware V6.0.10P2_TE and V6.0.10P3N3_TE.
Fixed versionsNo public fixed firmware/advisory located in the reviewed sources; researcher states no public ZTE fix was found as of 2026-05-18. Treat patch status as vendor-unpublished/unknown until your ISP or ZTE channel confirms otherwise.
Exposure and scanningThe public GitHub write-up says roughly 500 H188A interfaces were internet-reachable at original reporting time. That is not huge, but it is enough to matter for exposed branch or home-office gear.
Disclosure timelineCVE published 2026-03-30; public Full Disclosure advisory posted 2026-05-20.
Researcher / reporting orgMina Nageh Salalma (Monx Research).
04 · The Call

noisgate verdict.

Final Verdict
DOWNGRADED to MEDIUM (5.9/10)

The single biggest factor is the adjacent-network requirement: this is usually a post-initial-access or same-LAN problem, not a true internet-wide unauthenticated edge exploit. That sharply cuts the reachable population even though the resulting impact can be admin-level on affected routers.

HIGH Affected versions and basic vulnerability mechanics
MEDIUM Real-world exposure prevalence in enterprise fleets
MEDIUM Whether all validated devices convert disclosure into full admin access

Why this verdict

  • Downgrade from vendor HIGH for attacker position: AV:A means the attacker typically needs same-LAN or management-plane reachability first. In enterprise terms, that usually implies branch compromise, guest-network access, or a misconfiguration already put the attacker close to the router.
  • Downgrade for narrow population: this is a specific ZTE CPE/router model on two named firmware builds, not a ubiquitous enterprise platform. Reachable population is materially smaller than a mainstream firewall, VPN, hypervisor, or identity product.
  • Keep it at MEDIUM, not LOW: once reachable, exploitation is trivial, unauthenticated, and can expose secrets that the public research says lead to practical admin bypass. Compromising a branch or home-office edge device is still operationally meaningful because it can enable traffic manipulation and local pivoting.

Why not higher?

This is not a broad unauthenticated internet RCE on a common enterprise control plane. The chain depends on adjacency or equivalent management reachability, and that prerequisite compounds with the niche device population to suppress real-world exploitation volume.

Why not lower?

Calling this LOW would ignore the fact that there is public PoC material, no authentication is required once the interface is reachable, and the leak can cross into administrative control on validated devices. For organizations that actually deploy these routers at branches or home offices, the impact to the affected node is too strong for backlog-only treatment.

05 · Compensating Control

What to do — in priority order.

  1. Block management-plane reachability — Restrict the router web UI to a dedicated admin segment or jump host and remove guest, user, and WAN access. For a MEDIUM verdict there is no noisgate mitigation SLA, but this is the fastest risk reduction while you confirm patch availability.
  2. Disable remote administration — Turn off WAN-side or ISP-exposed administration anywhere it is not strictly required. This removes the small but important subset of devices that turn an adjacent bug into a remotely reachable one; do it as part of the 365-day remediation window if you cannot do it immediately.
  3. Rotate dependent secrets — Change router admin credentials, WLAN PSKs, and PPPoE credentials where operationally possible, especially if the device may have been reachable from guest or untrusted segments. This matters because the published research ties leaked WLAN material to the default admin password behavior on validated devices.
  4. Segment branch and guest networks — Ensure guest Wi-Fi and untrusted LANs cannot reach the router management IP. This specifically attacks the AV:A prerequisite that makes the bug exploitable in the first place.
  5. Monitor for wizard-endpoint abuse — Alert on HTTP requests containing _type=tedataNotLoginData, _tag=wizard_lua.lua, or IF_ACTION=getPassword|wlan_get|ppp_get. Detection is weak on consumer-grade routers, so upstream firewall, proxy, or packet telemetry is where you will get visibility.
What doesn't work
  • Password policy alone does not fix the unauthenticated read path; the bug leaks secrets before login, and on validated devices the WLAN secret may itself feed admin access.
  • EDR is largely irrelevant here because the target is a router/CPE device that usually has no host telemetry agent.
  • User MFA on enterprise apps does nothing for the router web UI if the device itself exposes pre-auth wizard handlers.
06 · Verification

Crowdsourced verification payload.

Run this from an auditor workstation on the same network segment that can reach the router web UI, not on the router itself. Invoke it as python3 verify_cve_2026_34472.py http://192.168.1.1; it needs no credentials and no elevated privileges, only HTTP reachability to the target management IP.

noisgate-verify.py
PYTHONREAD-ONLYSAFE
#!/usr/bin/env python3
# verify_cve_2026_34472.py
# Check ZTE ZXHN H188A for unauthenticated wizard credential disclosure
# Exit codes: 0=VULNERABLE, 1=PATCHED, 2=UNKNOWN

import sys
import urllib.request
import urllib.error

TIMEOUT = 8
LOGIN_MARKERS = [b'login', b'logon', b'username', b'password', b'adminLogin', b'quicksetup']
SENSITIVE_MARKERS = [b'pppoe', b'ssid', b'wlan', b'psk', b'password', b'key']
PATHS = [
    '/?_type=tedataNotLoginData&_tag=wizard_lua.lua&IF_ACTION=getPassword',
    '/?_type=tedataNotLoginData&_tag=wizard_lua.lua&IF_ACTION=wlan_get',
    '/?_type=tedataNotLoginData&_tag=wizard_lua.lua&IF_ACTION=ppp_get'
]

def fetch(url):
    req = urllib.request.Request(url, headers={'User-Agent': 'noisgate-verifier/1.0'})
    try:
        with urllib.request.urlopen(req, timeout=TIMEOUT) as resp:
            status = getattr(resp, 'status', 200)
            body = resp.read(8192)
            ctype = resp.headers.get('Content-Type', '')
            return status, ctype, body
    except urllib.error.HTTPError as e:
        try:
            body = e.read(4096)
        except Exception:
            body = b''
        return e.code, '', body
    except Exception:
        return None, '', b''

def normalize_base(base):
    base = base.strip()
    if not base.startswith('http://') and not base.startswith('https://'):
        base = 'http://' + base
    return base.rstrip('/')

def looks_sensitive(body):
    low = body.lower()
    hits = sum(1 for marker in SENSITIVE_MARKERS if marker in low)
    login_hits = sum(1 for marker in LOGIN_MARKERS if marker in low)
    return hits >= 2 and login_hits == 0

def main():
    if len(sys.argv) != 2:
        print('UNKNOWN - usage: python3 verify_cve_2026_34472.py <router_base_url>')
        sys.exit(2)

    base = normalize_base(sys.argv[1])
    saw_auth_block = False
    saw_response = False

    for path in PATHS:
        url = base + path
        status, ctype, body = fetch(url)
        if status is None:
            continue
        saw_response = True

        if status in (401, 403):
            saw_auth_block = True
            continue

        if status == 200 and looks_sensitive(body):
            print('VULNERABLE - unauthenticated wizard endpoint returned credential-like data via ' + path)
            sys.exit(0)

        low = body.lower()
        if any(marker in low for marker in LOGIN_MARKERS):
            saw_auth_block = True

    if saw_auth_block and saw_response:
        print('PATCHED - target responded but wizard reads appear gated or redirected to login')
        sys.exit(1)

    if saw_response:
        print('UNKNOWN - target responded but no conclusive credential disclosure was observed')
    else:
        print('UNKNOWN - no HTTP response from target or management UI unreachable')
    sys.exit(2)

if __name__ == '__main__':
    main()
07 · Bottom Line

If you remember one thing.

TL;DR
Monday morning: identify whether you actually have ZTE ZXHN H188A routers on firmware V6.0.10P2_TE or V6.0.10P3N3_TE, especially in branch and home-office inventories, then immediately remove management access from guest/user/WAN paths and rotate router/WLAN/PPPoE secrets where exposure is plausible. Because this is MEDIUM, there is no noisgate mitigation SLA — go straight to the 365-day remediation window unless you discover the interface is internet-exposed, in which case treat access restriction as urgent operational containment; then obtain and apply any ISP or vendor-provided fixed firmware within the noisgate remediation SLA of 365 days, documenting cases where no public patch exists yet and tracking them for vendor follow-up.

Sources

  1. NVD CVE-2026-34472
  2. CVE Program record
  3. Full Disclosure advisory by Mina Nageh Salalma
  4. Researcher GitHub repo / technical breakdown
  5. Researcher public disclosure gist
  6. FIRST EPSS project
  7. CISA Known Exploited Vulnerabilities Catalog
  8. ZTE PSIRT contact page
Peer Review

What defenders are saying.

Submit a review attribution: handle + country only
0 flags selected · stored anonymously
Validation Results

Crowdsourced verification outputs.

Results submitted by users who ran the verification payload against their environment.