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-111705 Overview
CVE-2026-111705 is an Insecure Direct Object Reference (IDOR) vulnerability in Fuint, an open-source membership and marketing platform, through commit 57ec018. The flaw resides in the /clientApi/book/myBookDetail endpoint, which fails to validate ownership before returning booking records. Any authenticated member can supply arbitrary bookId values to retrieve other members' booking details, including contact names, mobile numbers, in-store verification codes, service dates, store identifiers, and remarks. Because bookId is an auto-increment integer, attackers can iterate sequentially to enumerate the full booking database. The issue is tracked under CWE-639: Authorization Bypass Through User-Controlled Key.
Critical Impact
Authenticated attackers can harvest personally identifiable information (PII) and verification codes belonging to arbitrary Fuint members by iterating sequential booking identifiers.
Affected Products
- Fuint membership marketing platform through commit 57ec018
- fuint-application module, specifically the ClientBookController client API
- BookItemServiceImpl service layer handling booking record retrieval
Discovery Timeline
- 2026-10-16 - CVE-2026-111705 published to the National Vulnerability Database
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-111705
Vulnerability Analysis
The vulnerability affects the myBookDetail handler in ClientBookController.java. The controller accepts a bookId request parameter supplied by any authenticated member and passes it directly to BookItemServiceImpl.getBookInfoById(). The service returns the matching booking record without verifying that the authenticated user owns the record or has any relationship to the booking.
Because the API performs authentication but omits authorization, membership credentials alone are sufficient to access data belonging to other tenants of the same deployment. Returned fields include contact name, mobile number, in-store verification code, service date, store, and remarks — information suitable for fraud, impersonation at the point of service, and secondary phishing campaigns.
Root Cause
The root cause is a missing ownership check in the booking lookup path. The service layer trusts the client-supplied bookId and queries the database by primary key without filtering on the authenticated member's userId. This is a textbook [CWE-639] authorization bypass pattern in which an authenticated session is treated as sufficient authority for any object reference.
Attack Vector
Exploitation requires only a valid member account on the target Fuint instance. The attacker authenticates, then issues sequential GET or POST requests to /clientApi/book/myBookDetail while incrementing the bookId parameter. Each response returns the targeted booking record in full. Because bookId is an auto-increment column, enumeration costs no reconnaissance effort. Technical reproduction details are documented in the HackMD IDOR Analysis and the VulnCheck Advisory. The vulnerable source paths are visible in the BookItemServiceImpl implementation and the ClientBookController controller.
Detection Methods for CVE-2026-111705
Indicators of Compromise
- High-volume sequential requests to /clientApi/book/myBookDetail from a single authenticated session
- Requests where the bookId parameter increments or decrements monotonically across short time windows
- A single userId or JWT subject retrieving booking records associated with many distinct member accounts
- Elevated 200-response rates against myBookDetail paired with unusual outbound data volumes from the application tier
Detection Strategies
- Instrument the myBookDetail endpoint to log the authenticated userId, the requested bookId, and the owning userId of the returned record. Alert when they diverge.
- Add rate-based web application firewall (WAF) rules that flag enumeration patterns on booking APIs.
- Correlate application logs with database audit trails to identify sessions reading records they do not own.
Monitoring Recommendations
- Baseline the normal request rate for /clientApi/book/* endpoints per member and alert on statistical outliers.
- Forward Fuint application logs to a central analytics platform and build dashboards tracking cross-account object access.
- Monitor egress traffic from the application server for bulk data transfers consistent with booking data exfiltration.
How to Mitigate CVE-2026-111705
Immediate Actions Required
- Audit deployments running Fuint at or before commit 57ec018 and inventory exposed /clientApi/book/myBookDetail endpoints.
- Apply a server-side ownership check that compares the booking record's owner userId against the authenticated session before returning data.
- Rotate any in-store verification codes that may have been exposed and notify affected members of potential PII disclosure.
- Review access logs for the myBookDetail endpoint to identify prior enumeration attempts.
Patch Information
At the time of publication, no official vendor patch is referenced in the NVD entry. Operators should track the Fuint GitHub repository for a fix that enforces ownership validation in BookItemServiceImpl.getBookInfoById() and in the ClientBookController.myBookDetail handler. Refer to the VulnCheck Advisory for ongoing remediation status.
Workarounds
- Deploy a reverse-proxy or WAF rule that rejects myBookDetail requests when the response body references a userId that does not match the session principal.
- Replace sequential auto-increment bookId values with unguessable identifiers such as UUIDs to raise the enumeration cost.
- Restrict /clientApi/book/myBookDetail to source IP ranges associated with trusted mobile or web clients where feasible.
- Temporarily disable the endpoint if the booking detail feature is non-essential to business operations until a patched version is deployed.
# Example nginx rule to rate-limit enumeration of myBookDetail
limit_req_zone $binary_remote_addr zone=bookdetail:10m rate=10r/m;
location /clientApi/book/myBookDetail {
limit_req zone=bookdetail burst=5 nodelay;
proxy_pass http://fuint_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

