The ZXHN H188A V6 router's pre-login wizard exposes a handler called getPassword. It returns the Wi-Fi passphrase. The router's default administrator password is that same passphrase, uppercased, which means an unauthenticated GET to /?_type=tedataNotLoginData&_tag=wizard_lua.lua&IF_ACTION=getPassword pulls the bytes and .upper() finishes the bypass. ZTE PSIRT declined CVE assignment in February 2026 as a "customer-specific requirement with low risk." MITRE assigned it anyway five weeks later.
CVE-2026-34472: ZTE H188A's Admin Password Is the Wi-Fi Password, Uppercased
pattern
cve
proof of concept
The wizard is reachable through one query parameter
The dispatcher for an H188A web request lives in router_logic_impl.lua:
function RouterLogicClass:__URL2RouterType(urlPath, queryTable)
local routerType, resourceTag
if #urlPath == 0 then
routerType = queryTable._type
if not routerType then
routerType, resourceTag = self:__URLPath2RouterType(urlPath)
else
resourceTag = queryTable._tag
endWhen the URL path is empty, a request to / or /?..., the function reads _type from the query table. If _type is present, the dispatcher uses it directly and reads _tag from the same query table. If _type is absent, the dispatcher falls back to __URLPath2RouterType, which is where the wizard's access gate lives.
The gate is a four-line check in urlpath_2type_modifier.lua:
local QuickSetupEnable = "0"
local QuiSetupTable = _G.cmapi.getinst("OBJ_WEB_QUICKSETUP_ID", "IGD")
if QuiSetupTable.IF_ERRORID == 0 then
QuickSetupEnable = QuiSetupTable.QuickSetupEnable
end
if QuickSetupEnable == "1" then
return "tedataNotLogin", nil
endQuickSetupEnable is a flag on the IGD object that the firmware sets to "1" during initial setup and clears to "0" once the administrator finishes the wizard. The intended contract is straightforward: during quick-setup mode, route every root-path request to tedataNotLogin, the unauthenticated wizard. After setup, route requests somewhere else.
The contract holds in the fallback branch. It does not hold in the branch above it. The first reachable assignment in __URL2RouterType is routerType = queryTable._type, and the function never visits __URLPath2RouterType when that assignment succeeds. An external caller writes ?_type=tedataNotLoginData&_tag=wizard_lua.lua on the query, the dispatcher honors it, and the wizard is selected by the request rather than by the device's mode.
The third file in the chain is Tedata_notLogin_wizard_page_manage.lua:
function WizardPageMgrClass.getDataFiles(routerType, resourceTag)
g_logger:debug("routerType=" .. routerType)
if usermgr:isLogined() then
return false
end
UpdateCurrentSess()
local file = ""
file = "../page_mgr/wizard_page_deps/" .. resourceTag
return true, {
{file = file}
}, nilThe only conditional is if usermgr:isLogined() then return false. The handler refuses logged-in users. It does not refuse anyone else. The Lua module that loads the wizard handler is the module whose authorization model is "you must not be authenticated."
The function then concatenates resourceTag directly into a file path under wizard_page_deps/ and returns the path for inclusion. The attacker-supplied tag was wizard_lua.lua. The handler selected is wizard_lua.lua. The dispatcher has been told what to load and by whom.
_type is the dispatcher's internal routing override
The _type query parameter is not a documented public API. It is the framework's internal routing key, the value RouterLogicClass writes to itself when its own internal layers compose a request to a sibling module. The underscore prefix is the convention. There is no other token in the codebase that says "do not accept this from the network"; there does not have to be, because the convention has held in every other call site the framework wrote.
queryTable in __URL2RouterType is built from the inbound HTTP request's URL parameters. The dispatcher reads _type from queryTable with security-relevant authority: the value selects which handler module runs, which is the decision that determines whether the wizard's pre-login bundle is reachable from the network at all. The convention is documentation. The reading is enforcement.
This is internal-only-by-convention, the same shape Next.js's x-middleware-subrequest header exhibited in CVE-2025-29927 and ActiveMQ's vm:// transport exhibited in CVE-2026-34197. A framework defines a parameter as internal-IPC-only, then reads it with security-relevant authority on every inbound network request. The "internal-only" status is the convention that nobody outside the framework's source tree would know to send the key. Once someone reads the source tree, six characters in the query string turn the gate off.
Uppercase is not a hash
The wizard handler selected by _tag=wizard_lua.lua accepts an IF_ACTION query parameter that picks the subroutine. Three of those subroutines are exercised by the public PoC:
GET /?_type=tedataNotLoginData&_tag=wizard_lua.lua&IF_ACTION=getPassword&BAND=5GHz&PASSTYPE=PSK
GET /?_type=tedataNotLoginData&_tag=wizard_lua.lua&IF_ACTION=wlan_get&BAND=5GHz
GET /?_type=tedataNotLoginData&_tag=wizard_lua.lua&IF_ACTION=ppp_getgetPassword returns a JSON body whose KeyPassphrase field is the WPA2 PSK. wlan_get returns the same network's ESSID. ppp_get returns the PPPoE UserName. Three values, each individually sensitive, none of which a wizard for a not-yet-set-up device should plausibly know.
The firmware does know them, because the wizard's purpose is to render them back to an operator on the LAN cable during initial setup. The wizard's contract is that the request originates from someone with physical or near-physical access to the freshly-unboxed router. The contract is in the handler name (tedataNotLogin), in the file path (wizard_page_deps/), in the isLogined check that excludes anyone holding an admin session. The contract is everywhere in the wizard module. It is not in the dispatcher.
KeyPassphrase, on its own, is a credential disclosure. On an H188A V6, it is the admin login secret with two character classes of work. The reverse-engineered default-password algorithm is wifi_password.upper(). There is no salt, no hash, no key-derivation function. There is no entropy added between the value the wizard returns and the value the login form expects. There are upper-case letters and lower-case letters, and a guest who pulled the PSK has both.
Uppercase is a labeling. The H188A's admin form accepts the casing the firmware writes during provisioning, which is the all-caps form. The attacker calls .upper() once and submits.
The same handler family also writes
The local validation captured getPassword, wlan_get, and ppp_get. The PoC ships only those. The repository's root-cause section notes that the same wizard handler family includes mutating branches calling cmapi.setinst, the firmware's configuration-write API:
if FP_ACTION == "Apply" then
while cgilua.POST["_InstID_" .. index] do
t_Data = {}
for j, k in pairs(WLANSETTING_PARA) do
t_Data[k] = cgilua.POST[k .. "_" .. index]
end
tError = cmapi.setinst(WLANSETTING_OBJNAME, cgilua.POST["_InstID_" .. index], t_Data)wizard_wlan_config_lua.lua accepts an FP_ACTION=Apply POST and writes WLAN settings into the device's configuration store, on the same _type=tedataNotLoginData reachability the read handlers use. The PoC stops at the reads because the disclosure was sufficient for the auth-bypass chain. The writes are reachable on the same gate.
ZTE's position is the third party to the record
ZTE PSIRT received the disclosure in May 2024. The vendor's last reply in that disclosure thread is dated 2024-05-10. Twenty-one months later, on 2026-02-02, ZTE PSIRT responded to the researcher's MITRE escalation by declining CVE assignment and characterizing the issue as a "customer-specific requirement with low risk." MITRE assigned CVE-2026-34472 on 2026-03-27 anyway. As of 2026-05-18, no public ZTE advisory or fixed firmware release exists.
The vendor's framing has two predicates. Both are public record. Both are checkable against the code.
"Customer-specific" would name a deployment-time configuration. The routing bug is in router_logic_impl.lua, the dispatcher every H188A V6 unit ships with. The _type branch is reached on every request whose URL path is empty, which is every request to /. The default-password derivation lives in the firmware's first-boot provisioning, not in a per-deployment policy. Two firmware identifiers were validated, V6.0.10P2_TE and V6.0.10P3N3_TE, and the dispatcher is shared across the branch.
"Low-risk" would survive a count. The original report noted roughly 500 publicly reachable management interfaces. Every customer with the device on a residential LAN exposes the same primitive to anyone joining the wireless network, including a guest who pulls the PSK and then opens the admin panel. The CVSS vector the assigner published is AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, no authentication required and confidentiality fully compromised. The vendor's "low-risk" and the assigner's PR:N/C:H are both on the record. They do not agree.
PoC: minanagehsalalma/cve-2026-34472-auth-bypass-zte-h188a-router
The leak and the lock are the same string. The shift key is what ZTE put between them.