Skip to main content
Vulnerability Database/CVE-2026-111697

CVE-2026-111697: HUIZHI ChargeOS Information Disclosure

CVE-2026-111697 is an insecure direct object reference flaw in HUIZHI ChargeOS that allows attackers to access sensitive user data including wallets and charging orders. This post covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111697 Overview

CVE-2026-111697 is an Insecure Direct Object Reference (IDOR) vulnerability in HUIZHI ChargeOS cloud through version 3.0.9. The flaw resides in the hcp-mp module, specifically within MeController and OrderController. These controllers trust client-supplied userId, openId, and orderNumber parameters without validating that the authenticated caller owns the referenced resource. Attackers with any valid session can enumerate sequential member identifiers against endpoints such as /me/getMemberBalanceByUserId and /order/orderDetail to read arbitrary members' wallet balances, credit information, profile data, and charging orders. The weakness is tracked under CWE-639: Authorization Bypass Through User-Controlled Key.

Critical Impact

Any authenticated user can read every other member's wallet balance, profile data, and charging order history by incrementing numeric identifiers in API requests.

Affected Products

  • HUIZHI ChargeOS cloud, all versions through 3.0.9
  • hcp-mp module — MeController member endpoints
  • hcp-mp module — OrderController order endpoints

Discovery Timeline

  • 2026-10-16 - CVE-2026-111697 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-111697

Vulnerability Analysis

The hcp-mp controllers expose member and order lookup endpoints that accept the target identifier directly from the request body or query string. The server authenticates the session but never confirms that the requested userId, openId, or orderNumber belongs to the caller. This is a textbook broken object-level authorization pattern in a REST backend.

The exposed data is financially sensitive. Member balance queries return wallet amounts and credit; order queries return charging session detail including station, timing, and payment information. Because member identifiers are sequential, an attacker can script enumeration across the entire user base. See the VulnCheck Security Advisory and HackMD IDOR Analysis for request/response traces.

Root Cause

The controllers delegate database lookups using the client-supplied identifier as the primary key without cross-checking the session principal. Reviewed source in MeController.java and OrderController.java shows no ownership check between the authenticated token subject and the requested object key.

Attack Vector

Exploitation requires only low-privileged access — a standard registered member account — and operates over the network against the public Mini-Program API. The attacker authenticates once, then issues sequential requests to /me/getMemberBalanceByUserId, /me/* profile endpoints, and /order/orderDetail, varying the userId or orderNumber by one each iteration. No special tooling, user interaction, or bypass of transport security is needed.

No verified proof-of-concept code is published in the enriched references. See the external advisories cited above for request-level technical details.

Detection Methods for CVE-2026-111697

Indicators of Compromise

  • High-rate GET or POST requests to /me/getMemberBalanceByUserId, /me/*, and /order/orderDetail from a single session.
  • Sequential or monotonically increasing values in the userId, openId, or orderNumber parameters within a short time window.
  • Successful HTTP 200 responses for member records that do not correspond to the authenticated session identity.

Detection Strategies

  • Correlate web access logs to flag any session where the userId parameter diverges from the session's bound user ID across multiple requests.
  • Baseline normal per-user call volume on hcp-mp endpoints and alert on deviations exceeding typical access patterns.
  • Deploy an API gateway or WAF rule that inspects request-body userId values against the JWT or session subject claim.

Monitoring Recommendations

  • Centralize hcp-mp application logs, API gateway logs, and authentication events for cross-source correlation.
  • Retain full request parameters (not just paths) for the affected endpoints to support retrospective hunting.
  • Alert on bulk access to sensitive fields such as balance, credit, and orderNumber originating from non-admin sessions.

How to Mitigate CVE-2026-111697

Immediate Actions Required

  • Restrict external exposure of the hcp-mp module and place the Mini-Program API behind a gateway that enforces session-to-identity binding.
  • Add server-side ownership checks in MeController and OrderController that compare the authenticated principal to the requested userId, openId, and orderNumber.
  • Audit access logs for prior enumeration activity across member and order endpoints and notify impacted members if data exfiltration is confirmed.

Patch Information

No vendor patch is identified in the enriched CVE data for HUIZHI ChargeOS cloud 3.0.9 or earlier. Operators should track the upstream repository referenced in the VulnCheck Security Advisory for a fixed release and apply code-level authorization changes in the interim.

Workarounds

  • Introduce an authorization filter or interceptor that rejects any request where the body-supplied userId or openId does not match the session subject.
  • Replace sequential numeric member identifiers with unguessable UUIDs to raise the cost of enumeration while an authorization fix is prepared.
  • Rate-limit the affected endpoints per session to reduce the viability of brute-force identifier enumeration.
bash
# Example reverse-proxy rule: block requests where body userId differs from JWT sub
# (nginx + njs pseudo-configuration)
location /me/ {
    js_content hcp.enforce_owner;
}
location /order/orderDetail {
    js_content hcp.enforce_owner;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.