CVE-2026-10168: OUSL-GROUP-BrinaryBrains School Student Management System Parents.php marks resource injection
A security vulnerability has been detected in OUSL-GROUP-BrinaryBrains School Student Management System up to 1e70e5ad1125b86dca4ee086eb6bb121f17708b6. Affected is the function marks of the file application/controllers/Parents.php. The manipulation of the argument param1 leads to improper control of resource identifiers. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.
Security readout for executives and security teams
Plain-English summary
CVE-2026-10168 affects the School Student Management System by OUSL-GROUP-BrinaryBrains. A remote authenticated user may be able to manipulate a marks-related parameter and access or affect resources they should not control. Public proof-of-concept disclosure is reported, but CISA KEV status is false and no cited source confirms active exploitation.
Executive priority
Treat this as a moderate, exposure-dependent issue. Prioritize if the affected system handles real student records or is internet-accessible. The main business risk is unauthorized viewing or modification of student marks, with uncertainty because vendor fix status is unclear.
Technical view
The issue is in application/controllers/Parents.php, function marks. Manipulating param1 leads to improper control of resource identifiers, mapped to CWE-99 and described by VulDB as resource injection/IDOR. CVSS v2 is 6.5 with network access, low complexity, and single authentication required. Affected code is listed up to commit 1e70e5ad1125b86dca4ee086eb6bb121f17708b6.
Likely exposure
Exposure appears limited to deployments of this specific School Student Management System, especially parent marks functionality reachable by authenticated remote users. The project uses rolling releases, so fixed and affected versions are not clearly named.
Exploitation context
The exploit has reportedly been publicly disclosed and may be used. However, KEV is false, and the provided sources do not establish active exploitation in the wild. The vendor/project was reportedly notified through an issue and had not responded.
Researcher notes
Evidence is primarily VulDB/CVE metadata plus a public GitHub issue. The affected surface is narrow but sensitive. Avoid assuming a patch exists; rolling-release versioning and no maintainer response leave remediation dependent on local code review, access restriction, or later upstream guidance.
Mitigation direction
Identify whether this application or fork is deployed.
Restrict access to parent marks functionality until vendor guidance is available.
Check the upstream issue and CVE sources for a fixed commit or release.
Review authorization around marks resource lookups in local forks.
Monitor application logs for suspicious marks-related access patterns.
Validation and detection
Inventory deployed commits and compare against 1e70e5ad1125b86dca4ee086eb6bb121f17708b6.
Confirm whether Parents.php marks is reachable by authenticated remote users.
Review tests or code paths proving users can only access authorized marks resources.
Check whether any upstream fix or maintainer response has appeared.
Look for unusual repeated access to marks resources in recent logs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-99: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-99 · source CWE mapping
Improper Control of Resource Identifiers ('Resource Injection')
Improper Control of Resource Identifiers ('Resource Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.