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-111352 Overview
CVE-2026-111352 is an incorrect authorization vulnerability [CWE-863] in ThinkCMF through version 8.0.1. The flaw resides in RestAdminBaseController where the Auth::check() function fails open when no admin_api rule is configured. Restricted backend administrators with a valid admin-type API token can call every admin REST API endpoint regardless of their assigned role.
Attackers abusing this flaw can enumerate member emails and mobile numbers, disable member accounts, and invoke PUT admin/roles/{id}/authorize to grant themselves full administrator rights. The vulnerability turns any low-privilege admin account into a full takeover vector.
Critical Impact
A low-privilege administrator can escalate to full administrator by calling the role authorization endpoint, exposing member PII and granting arbitrary privileges.
Affected Products
- ThinkCMF versions through 8.0.1
- cmf-core package (RestAdminBaseController, Auth.php)
- cmf-api package (RoleController)
Discovery Timeline
- 2026-10-15 - CVE-2026-111352 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-111352
Vulnerability Analysis
The vulnerability stems from how ThinkCMF enforces role-based access control on admin REST API routes. RestAdminBaseController delegates authorization decisions to the Auth::check() helper defined in cmf-core/src/lib/Auth.php. When the authenticated administrator's role has no rules configured under the admin_api category, the check returns a permissive result rather than denying access.
This fail-open behavior allows any administrator holding a valid admin-type API token to invoke endpoints they were never granted access to. Sensitive endpoints under admin/users, admin/members, and admin/roles become callable by restricted accounts. The attacker does not need to bypass authentication; they only need any admin-tier credential.
Root Cause
The root cause is logic in Auth::check() that treats the absence of defined rules for a resource category as implicit authorization. Combined with RestAdminBaseController's reliance on this helper as the sole access gate, every admin REST endpoint inherits the permissive default. The authorization model conflates "no rule configured" with "access allowed."
Attack Vector
An authenticated administrator with network access to the admin API submits HTTP requests using their issued API token. By calling GET admin/users or GET admin/members, the attacker enumerates member emails and mobile numbers. Issuing PUT admin/roles/{id}/authorize lets the attacker rewrite role permissions, including attaching full administrator rights to their own role.
See the HackMD Authorization Analysis and VulnCheck Security Advisory for complete endpoint and payload details. The vulnerable code paths are documented in the RestAdminBaseController source and the Auth.php source.
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-111352
Indicators of Compromise
- Unexpected PUT requests to admin/roles/{id}/authorize originating from non-super-admin accounts.
- Bulk GET requests to admin/users or admin/members endpoints enumerating member records.
- Admin role records modified outside of change-management windows, especially additions to high-privilege rule sets.
- New administrator accounts or privilege grants created shortly after a low-privilege admin login.
Detection Strategies
- Audit application logs for admin API calls where the caller's role lacks a matching admin_api rule entry.
- Correlate API token identifiers with the HTTP endpoints they invoke to flag out-of-scope access.
- Alert on sequences where a single session issues read requests against member PII followed by writes to the role authorization endpoint.
Monitoring Recommendations
- Enable verbose request logging for all routes under /api/admin/ and ship logs to a centralized analytics platform.
- Track changes to the role and role_user database tables and alert on privilege expansions.
- Monitor outbound traffic from the application server for unusual export volumes that may indicate PII exfiltration.
How to Mitigate CVE-2026-111352
Immediate Actions Required
- Restrict network access to the ThinkCMF admin API to trusted administrator IP ranges only.
- Revoke existing admin-type API tokens and reissue them to accounts that genuinely require admin API access.
- Review all configured roles and remove any admin accounts whose privileges exceed operational need.
- Inspect the role table for unauthorized privilege changes and roll back any suspicious modifications.
Patch Information
At the time of publication, no fixed version has been identified in the NVD record for versions through 8.0.1. Monitor the ThinkCMF GitHub repositories for security releases that correct the Auth::check() fail-open behavior and tighten RestAdminBaseController authorization. Review the VulnCheck Security Advisory for the latest remediation guidance.
Workarounds
- Place the admin API behind a reverse proxy that enforces source IP allow-listing and mutual TLS.
- Configure explicit admin_api rules for every administrator role so that Auth::check() has rules to evaluate rather than defaulting open.
- Disable or remove unused admin accounts and enforce least-privilege role assignments.
- Deploy a web application firewall rule to block PUT requests to admin/roles/{id}/authorize from untrusted sources.
# Example WAF rule concept to block role authorization abuse
# Block PUT admin/roles/{id}/authorize unless source IP is in admin allow-list
SecRule REQUEST_METHOD "@streq PUT" \
"chain,id:1026111352,phase:2,deny,status:403,msg:'Block ThinkCMF role authorize abuse'"
SecRule REQUEST_URI "@rx ^/api/admin/roles/[0-9]+/authorize$" \
"chain"
SecRule REMOTE_ADDR "!@ipMatch 10.0.0.0/8,192.168.0.0/16"
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

