<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>ThinkCMF - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/thinkcmf/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 15 Oct 2026 22:50:19 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/thinkcmf/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Incorrect Authorization Vulnerability in ThinkCMF RestAdminBaseController</title><link>https://feed.craftedsignal.io/briefs/2026-10-thinkcmf-auth-bypass/</link><pubDate>Thu, 15 Oct 2026 22:50:19 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-thinkcmf-auth-bypass/</guid><description>An incorrect authorization flaw in ThinkCMF RestAdminBaseController allows restricted administrators to bypass access controls, leading to privilege escalation and unauthorized data access.</description><content:encoded><![CDATA[<p>ThinkCMF versions through 8.0.1 are vulnerable to an incorrect authorization flaw located within the RestAdminBaseController. The vulnerability originates from the Auth::check() function, which fails to enforce access control when no explicit 'admin_api' rule is defined for a given endpoint. This failure results in an open state, granting access to restricted REST API endpoints to any user possessing a valid admin-type API token.</p>
<p>An attacker with low-level administrative credentials can exploit this misconfiguration to interact with restricted API methods. This scope includes the ability to exfiltrate sensitive member data, such as email addresses and mobile numbers, the ability to disable user accounts, and the critical capability to invoke the PUT admin/roles/{id}/authorize endpoint to escalate their own account privileges to full administrator. This vulnerability poses a significant risk to the integrity and confidentiality of the ThinkCMF management environment.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains access to a low-privilege administrative API token via credential compromise or insider access.</li>
<li>Attacker inspects application API endpoints to identify routes handled by RestAdminBaseController.</li>
<li>Attacker crafts a malicious HTTP PUT request directed at the /admin/roles/{id}/authorize endpoint.</li>
<li>The application triggers RestAdminBaseController which calls the flawed Auth::check() function.</li>
<li>Auth::check() fails to validate the request because no specific 'admin_api' rule is present, bypassing the permission check.</li>
<li>The application processes the request, granting the attacker's target account full administrative permissions.</li>
<li>Attacker logs in with the elevated account to perform full administrative management or data exfiltration.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-111352 allows unauthorized users to perform sensitive administrative actions. This includes unauthorized access to user databases (emails, mobile numbers), disruption of service through account disabling, and full privilege escalation to the super-administrator level, which can result in a total compromise of the application and underlying data.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor web server logs for high-frequency or unauthorized calls to /admin/roles/{id}/authorize or endpoints returning sensitive user metadata.</li>
<li>Audit current administrative API permissions and ensure all custom endpoints have explicit 'admin_api' rules defined within the controller logic.</li>
<li>Evaluate the necessity of all active admin-type API tokens and revoke those associated with compromised or inactive accounts.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>privilege-escalation</category><category>web</category></item></channel></rss>