Quick answers
- Is CVE-2026-10167 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10167 being exploited in the wild.
- How severe is CVE-2026-10167?
- High severity, with a CVSS score of 7.3, published 31 May 2026.
- Which products and versions are affected?
- OUSL-GROUP-BrinaryBrains School Student Management System up to 1e70e5ad1125b86dca4ee086eb6bb121f17708b6.
- Is there a fix for CVE-2026-10167?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-10167 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-10167?
- Check whether you run OUSL-GROUP-BrinaryBrains School Student Management System at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authentication bypass vulnerability exists in the `sign_auth_cookie` function within `application/controllers/Login.php` (part of `MY_Controller`). The application uses a hardcoded encryption key ('Signetbd') in `application/config/config.php` to generate HMAC-SHA256 signatures for the `school_auth` cookie. Because the key is static and publicly known, a remote, unauthenticated attacker can forge a valid `school_auth` cookie for any role (e.g., admin, teacher) and user ID. When the server processes this forged cookie via `restore_auth_session_from_cookie()`, it validates the signature against the hardcoded key and establishes a valid session, granting the attacker full access to the impersonated account. As of the advisory date, no patch has been released by the vendor.
Affected products
- OUSL-GROUP-BrinaryBrains School Student Management System up to 1e70e5ad1125b86dca4ee086eb6bb121f17708b6
Timeline
- 2026-05-04: disclosed: Issue reported to the project on GitHub
- 2026-05-31: advisory: CVE published and NVD record created