/

CVE-2026-34472

Severity:

HIGH RISK

(7.1)

Authentication Bypass and Information Disclosure

CVE-2026-34472

Modified

Vulnerability type

Category:

Authentication Bypass and Information Disclosure

CWE:

CWE-200, CWE-306

Impact:

Unauthorized Access and Credential Disclosure

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The ZTE ZXHN H188A router exposes sensitive credentials through its web-based setup wizard without requiring authentication.

An unauthenticated attacker on the local network can retrieve admin, WLAN, and PPPoE credentials, and in some cases may change configuration settings, leading to loss of control over the router and attached network.

Affected context

This vulnerability occurs in the web management "wizard" or initial setup interface of ZTE ZXHN H188A routers running affected firmware versions.

It manifests when the router:

  • Exposes the web management interface on the local network (e.g., default LAN IP and port),
  • Fails to enforce authentication on specific wizard-related endpoints or flows, and
  • Returns configuration data containing sensitive credentials in responses or page content.

The issue is typically reachable from any device on the local network segment that can open the router's web UI, assuming default or typical access settings.

Exploit preconditions

  • Attack surface: Router web management interface, specifically the setup/wizard pages.
  • Network position: Attacker must have layer-3 access to the router's LAN IP (e.g., connected via Wi‑Fi or Ethernet, or otherwise on the local network).
  • Required access: No prior authentication; only network reachability to the HTTP/HTTPS interface.
  • Trigger point: Accessing or invoking the wizard interface endpoints that return configuration data or accept changes without enforcing a logged-in session.
  • Why exploitation is possible: The router does not correctly enforce authentication (CWE-306) on certain wizard resources and returns sensitive information in clear form (CWE-200), allowing an unauthenticated client to access information and potentially submit configuration changes.

Why this happens

The underlying problem is a broken enforcement of access control and session checks on the router's wizard interface.

Certain HTTP endpoints or logic paths that support initial setup or configuration do not validate that the requester is an authenticated administrator, yet they still:

  • Read and serialize sensitive configuration values (admin password, WLAN PSK, PPPoE credentials), and/or
  • Accept and apply configuration changes.

This maps to CWE-306: Missing Authentication for Critical Function, where critical operations are exposed without verifying user identity.

Because these endpoints also reveal sensitive configuration values in their responses, the issue is simultaneously an information disclosure vulnerability in line with CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.

At a design level, the wizard flow treats local network access as implicitly trusted and fails to bind sensitive operations to an authenticated session, leading to credential leakage and unauthorized configuration control.

Potential impact

  • An attacker on the local network may obtain the router's administrator username and password.
  • WLAN pre-shared keys (Wi‑Fi passwords) can be disclosed, enabling unauthorized wireless access.
  • PPPoE or ISP credentials can be retrieved, potentially exposing subscriber-specific information or enabling misuse on other devices.
  • Router configuration may be altered without authorization, such as changing DNS servers, firewall settings, or Wi‑Fi parameters.
  • Network traffic could be redirected or intercepted via malicious DNS or routing changes.
  • Full loss of control over the router's management interface for legitimate users, including lockout or persistent compromise.

General mitigation guidance

Effective mitigation usually focuses on enforcing strict authentication and reducing implicit trust in local-network access:

  • Require a valid, authenticated administrative session for all endpoints that read or modify configuration, including setup and wizard flows.
  • Centralize access control so that every HTTP handler for management features checks authentication and authorization consistently.
  • Avoid returning sensitive fields (admin password, WLAN keys, PPPoE credentials) in UI/API responses; when necessary for display, consider masked values or one-way representations.
  • Separate "first-time setup" logic from normal runtime behavior, and ensure that once initial provisioning is complete, wizard endpoints are disabled or fully protected by authentication.
  • Limit exposure of the management interface (e.g., non-default ports, optional interface binding) and encourage deployment with strong, unique admin and Wi‑Fi credentials by default.
  • Apply least-privilege design to configuration operations so that even authenticated actions are constrained to the minimum required scope.

How teams detect issues like this

Detection approaches can combine black-box testing, configuration review, and code-level analysis:

  • Black-box testing:
  • Probe wizard and setup URLs without logging in to confirm whether configuration data or change operations are accessible.
  • Intercept HTTP traffic (using a proxy) to inspect responses for embedded credentials or sensitive fields.
  • Static analysis and code review:
  • Search for controller/handler functions associated with setup, wizard, or initialization pages that bypass or omit authentication middleware or session checks.
  • Flag any code paths that serialize or echo configuration objects containing passwords, keys, or ISP credentials directly into HTTP responses.
  • Verify that all management endpoints are behind a consistent authentication and authorization layer rather than ad hoc checks.
  • Policy enforcement:
  • Establish secure coding standards requiring authentication for all management and configuration features.
  • Integrate automated security scanning or SAST tools into the firmware development pipeline to detect missing authentication checks and sensitive data exposures.
  • Runtime monitoring (where feasible):
  • Monitor access logs for unauthenticated access to management endpoints and unexpected configuration change requests.

Sources

SourceLink
gist.github.comgist.github.com/minanagehsalalma/7a8516b9b00d0008f2f25750320560c9
zte.com.cnzte.com.cn/global/
seclists.orgseclists.org/fulldisclosure/2026/May/19

Frequently asked

questions

Typically, exploitation is limited to the local network, as the router's web management interface is usually bound to the LAN side. However, if remote management is exposed to the internet or if the router is reachable via some upstream misconfiguration, the risk can extend beyond the local network.

The attacker generally only needs IP connectivity to the router's management interface on the local network. No valid administrator credentials are required; connecting via Wi‑Fi (e.g., guest or compromised client) or Ethernet is usually sufficient.

The safest pattern is to ensure all management and configuration endpoints, including setup and wizard pages, are consistently protected by strong authentication and session management. Additionally, sensitive credentials should never be returned in cleartext in UI or API responses, even to authenticated users, unless absolutely necessary and handled in a tightly controlled way.

Future designs should treat local network traffic as untrusted, enforce centralized authentication and authorization for every management feature, and minimize how and where sensitive data is handled. Security reviews and automated checks should be applied to all configuration and setup flows to ensure that no unauthenticated paths can read or modify critical settings or expose credentials.

Find out what's already
exploitable in your codebase.