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-111698 Overview
CVE-2026-111698 is a missing authorization vulnerability affecting HUIZHI ChargeOS cloud through version 3.0.9. The flaw resides in the hcp-mp module's PayController.xcxRecharge endpoint, which fails to verify that the authenticated caller owns the target wallet. Attackers can submit requests containing arbitrary amount and userId parameters to credit or reduce any member's wallet balance without processing a real payment. The result is free consumption of charging services and direct manipulation of stored financial values. The weakness is classified under CWE-639: Authorization Bypass Through User-Controlled Key.
Critical Impact
Any low-privileged account can modify any other member's wallet balance and consume charging services for free, directly impacting billing integrity.
Affected Products
- HUIZHI ChargeOS cloud through version 3.0.9
- Component: hcp-mp module, PayController class
- Endpoint: xcxRecharge (WeChat Mini Program recharge handler)
Discovery Timeline
- 2026-10-16 - CVE-2026-111698 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-111698
Vulnerability Analysis
The vulnerability is an Insecure Direct Object Reference (IDOR) in the WeChat Mini Program (hcp-mp) recharge flow. The xcxRecharge endpoint in PayController.java accepts a userId parameter from the client and uses it directly to look up and credit the target wallet. No server-side check compares the submitted userId with the authenticated session identity.
A second logic defect compounds the issue: the controller credits the wallet based on the request's amount field without first confirming that WeChat Pay returned a successful transaction. Together, these flaws turn a payment endpoint into a wallet-write primitive available to any authenticated user.
Root Cause
The root cause is missing authorization and missing payment verification in com.hcp.mp.controller.PayController.xcxRecharge. The handler trusts user-supplied userId and amount values and performs a database update without correlating them to the current session or to a verified payment callback. This is a textbook CWE-639 pattern where authorization decisions depend on a user-controlled key.
Attack Vector
An attacker authenticates to the Mini Program with any valid account, then issues a crafted HTTP request to the xcxRecharge endpoint supplying the victim's userId and an arbitrary amount. The server updates the targeted wallet balance and returns a successful response. The attacker can then consume charging services for free, inflate their own balance, or reduce another member's balance. See the VulnCheck Security Advisory, the HackMD IDOR Analysis, and the vulnerable GitHub source for the exact handler code.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-111698
Indicators of Compromise
- Requests to the xcxRecharge endpoint where the request body userId does not match the authenticated session's user identifier.
- Wallet balance increases on member accounts without a corresponding WeChat Pay transaction identifier in payment logs.
- Repeated recharge requests from a single session targeting multiple distinct userId values.
- Charging sessions completed by accounts whose balance history shows unverifiable credits.
Detection Strategies
- Perform application-layer log review correlating xcxRecharge calls to WeChat Pay callback records; flag any credit without a matching paid transaction.
- Add server-side instrumentation to compare the session principal against the userId parameter and log mismatches as high-severity events.
- Hunt in database audit logs for wallet balance mutations that lack an associated payment order ID.
Monitoring Recommendations
- Alert on anomalous volumes of recharge API calls per authenticated user, especially those targeting multiple userId values.
- Monitor for free-of-charge charging sessions concentrated on specific accounts or station IDs.
- Ingest ChargeOS application logs into a centralized SIEM to retain evidence of IDOR exploitation attempts.
How to Mitigate CVE-2026-111698
Immediate Actions Required
- Restrict external exposure of the hcp-mpxcxRecharge endpoint until a fix is applied, for example via WAF rules or API gateway policy.
- Rebuild PayController.xcxRecharge to derive the target userId from the authenticated session instead of the request body.
- Validate every recharge against the WeChat Pay server-to-server notification before mutating wallet balance.
- Audit wallet balance history for the exposure window and reverse unverifiable credits.
Patch Information
No vendor patch is referenced in the current advisory data. Operators should track the project repository and the VulnCheck Security Advisory for an official fix. Until a vendor release is available, apply code-level remediation in com.hcp.mp.controller.PayController to enforce authorization and verify payment status before any balance update.
Workarounds
- Enforce an API gateway rule that rejects xcxRecharge requests where the body userId differs from the authenticated token's subject claim.
- Deploy a WAF signature that blocks requests to xcxRecharge lacking a corresponding WeChat Pay transaction_id field.
- Disable the Mini Program recharge path and route top-ups through a verified payment workflow until code is remediated.
# Example API gateway rule (nginx + njs pseudocode) rejecting userId mismatches
location /hcp-mp/pay/xcxRecharge {
js_content pay.enforce_userid_match;
# pay.enforce_userid_match compares JWT 'sub' with JSON body 'userId'
# and returns 403 on mismatch before proxying upstream
proxy_pass http://chargeos_backend;
}
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

