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-111699 Overview
CVE-2026-111699 is an authentication bypass vulnerability in Niefy wx-api through version 0.8.2. The flaw allows unauthenticated attackers to impersonate WeChat fans by supplying a raw openid cookie to fan-facing controllers. An attacker who knows a victim's openid can call the /wxUser/getUserInfo and /wxUserTags endpoints to read nickname, phone number, unionid, and assigned tags. The attacker can also add or remove fan tags, modifying downstream segmentation logic. The weakness is tracked as missing authentication for a critical function [CWE-306].
Critical Impact
Unauthenticated attackers can read WeChat fan personally identifiable information (PII) and manipulate fan tags by presenting any known openid as a cookie value.
Affected Products
- Niefy wx-api versions through 0.8.2
- WxUserController fan-facing endpoints (/wxUser/getUserInfo)
- WxUserTagsController fan-facing endpoints (/wxUserTags)
Discovery Timeline
- 2026-10-16 - CVE-2026-111699 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-111699
Vulnerability Analysis
Niefy wx-api is a Java Spring application that integrates with WeChat Official Accounts. The application uses Apache Shiro for access control. The ShiroConfig filter chain declares the fan-facing routes as anonymous, meaning no authentication filter runs before controller invocation. Controllers then trust a client-supplied openid cookie as the identity of the requester.
The WxUserController.getUserInfo handler reads the openid cookie and uses it directly as a database lookup key. The WxUserTagsController endpoints apply the same pattern for tag read, add, and remove operations. No session token, signature, or server-side binding verifies that the caller actually controls the referenced WeChat account.
An attacker who learns a victim's openid can harvest profile data including nickname, phone number, and unionid. The attacker can also attach or detach fan tags, which affects downstream marketing automation and audience targeting.
Root Cause
The root cause is missing server-side verification of the identity claim transported in the openid cookie [CWE-306]. The Shiro filter chain exempts fan endpoints from authentication, and controllers treat an unauthenticated cookie value as an authoritative principal.
Attack Vector
Exploitation is remote and unauthenticated. An attacker sends an HTTP request to /wxUser/getUserInfo or /wxUserTags with a Cookie: openid=<victim_openid> header. The server returns the victim's fan record or applies the requested tag mutation. Attack complexity is elevated because the attacker must first obtain a valid openid, which may be enumerated, leaked, or guessed in bounded contexts.
For source-level details, review the GitHub ShiroConfig Code Review, the GitHub WxUserController Code Review, and the GitHub WxUserTagsController Code Review.
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-111699
Indicators of Compromise
- Inbound HTTP requests to /wxUser/getUserInfo or /wxUserTags carrying only an openid cookie and no session identifier.
- Repeated requests from a single source IP iterating distinct openid values, indicating enumeration.
- Unexpected fan tag add or remove operations in application logs that do not correlate to administrator or legitimate fan activity.
Detection Strategies
- Instrument web access logs to flag requests to fan-facing endpoints where the openid cookie is the sole credential presented.
- Correlate tag mutation events against the source IP reputation and WeChat webhook origin ranges to identify out-of-band callers.
- Alert on bursts of /wxUser/getUserInfo responses containing distinct unionid or phone values returned to the same client.
Monitoring Recommendations
- Forward application and reverse-proxy logs to a centralized analytics platform for cross-session correlation.
- Track rate and diversity of openid cookie values per source IP as a baseline deviation signal.
- Review the HackMD IDOR and Unauth Analysis and the VulnCheck Advisory on Authentication Bypass for additional detection context.
How to Mitigate CVE-2026-111699
Immediate Actions Required
- Restrict public exposure of /wxUser/* and /wxUserTags endpoints to trusted WeChat callback sources using network-level allow-listing.
- Remove reliance on the raw openid cookie by requiring a server-issued session token bound to the authenticated WeChat login flow.
- Audit application logs for prior unauthorized access to fan PII and rotate exposed records where contractual obligations require.
Patch Information
At the time of publication, no fixed version is listed in the NVD entry for Niefy wx-api beyond 0.8.2. Monitor the upstream repository and the VulnCheck Advisory on Authentication Bypass for a vendor fix.
Workarounds
- Modify the ShiroConfig filter chain so fan endpoints require an authenticated subject rather than the anon filter.
- Replace cookie-based openid trust with a signed JWT or Shiro session cookie generated after WeChat OAuth code exchange.
- Deploy a reverse-proxy rule that strips inbound openid cookies and injects an identity header only after validating a server-side session.
# Example nginx rule to drop client-supplied openid cookies before upstream
location /wxUser/ {
proxy_set_header Cookie "";
proxy_pass http://wx_api_upstream;
}
location /wxUserTags {
proxy_set_header Cookie "";
proxy_pass http://wx_api_upstream;
}
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

