<?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/"><channel><title>OUSL-GROUP-BrinaryBrains — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/ousl-group-brinarybrains/</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>Sun, 31 May 2026 05:17:54 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/ousl-group-brinarybrains/feed.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-10167 Improper Authentication in OUSL-GROUP-BrinaryBrains School Student Management System</title><link>https://feed.craftedsignal.io/briefs/2026-05-cve-2026-10167/</link><pubDate>Sun, 31 May 2026 05:17:54 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-cve-2026-10167/</guid><description>CVE-2026-10167 is an improper authentication vulnerability in OUSL-GROUP-BrinaryBrains School Student Management System allowing a remote attacker to manipulate the 'role' argument to bypass authentication.</description><content:encoded><![CDATA[<p>CVE-2026-10167 identifies an improper authentication vulnerability within the OUSL-GROUP-BrinaryBrains School Student Management System, affecting versions up to 1e70e5ad1125b86dca4ee086eb6bb121f17708b6. This vulnerability resides in the <code>sign_auth_cookie</code> function of the <code>application/controllers/Login.php</code> file, specifically within the <code>MY_Controller</code> component. A remote attacker can exploit this flaw by manipulating the <code>role</code> argument, leading to unauthorized access. The exploit is publicly available, increasing the risk of active exploitation. The vendor employs rolling releases, making specific affected versions difficult to pinpoint. The project has been notified of the vulnerability but has yet to respond.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies the <code>sign_auth_cookie</code> function within <code>application/controllers/Login.php</code>.</li>
<li>Attacker crafts a malicious HTTP request targeting the vulnerable function.</li>
<li>The HTTP request includes a manipulated <code>role</code> argument designed to bypass authentication checks.</li>
<li>The server-side application processes the crafted request without proper validation of the <code>role</code> parameter.</li>
<li>The application&rsquo;s authentication logic incorrectly grants access based on the attacker-supplied <code>role</code>.</li>
<li>The attacker gains unauthorized access to the system with elevated privileges.</li>
<li>Attacker performs actions they are not authorized to do.</li>
<li>Attacker potentially exfiltrates sensitive student data or modifies system settings.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-10167 allows unauthorized remote attackers to bypass authentication and gain elevated privileges within the OUSL-GROUP-BrinaryBrains School Student Management System. This can lead to sensitive data breaches, modification of student records, and disruption of school operations. The lack of a vendor response increases the urgency for defenders to implement mitigating controls. Given the public availability of the exploit, attacks are likely to occur.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor web server logs for requests targeting <code>application/controllers/Login.php</code> with suspicious manipulation of the <code>role</code> parameter. Deploy the Sigma rule <code>Detect Suspicious Role Parameter Manipulation</code> to identify potential exploitation attempts.</li>
<li>Implement input validation and sanitization on the <code>role</code> parameter within the <code>sign_auth_cookie</code> function to prevent malicious manipulation.</li>
<li>Apply rate limiting to the authentication endpoint to mitigate brute-force attempts to exploit the vulnerability.</li>
<li>Consider deploying a web application firewall (WAF) rule to block requests that match the exploit pattern.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>cve-2026-10167</category><category>improper-authentication</category><category>web-application</category></item></channel></rss>