Authorization Bypass Through User-Controlled Key vulnerability in PROLIZ Computer Software Hardware Service Trade Ltd. Co. OBS (Student Affairs Information System) allows Parameter Injection.
This issue affects OBS (Student Affairs Information System): before v26.0328.
Security readout for executives and security teams
Plain-English summary
CVE-2025-0875 is an authorization weakness in Proliz OBS, a Student Affairs Information System. A logged-in user may be able to access data by manipulating a user-controlled key. The main business risk is unauthorized exposure of student affairs information, not system takeover or service outage.
Executive priority
Treat as a near-term data confidentiality issue for institutions using Proliz OBS. Prioritize inventory and remediation where student records or personal data are stored, especially if many users have login access.
Technical view
The CVE describes CWE-639, Authorization Bypass Through User-Controlled Key, in PROLIZ OBS before v26.0328. The CVSS 3.1 score is 6.5: network reachable, low complexity, low privileges required, no user interaction, high confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is limited to organizations running PROLIZ OBS versions before v26.0328. The flaw requires some authenticated access, so public internet exposure is less decisive than whether untrusted or broad user populations can log in.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. The described weakness is an IDOR-style access-control issue, commonly exploited by changing identifiers, but no exploit details are provided in the source bundle.
Researcher notes
Evidence is limited to CVE metadata and Turkish government advisory references. One listed USOM link is marked broken in the bundle. No public exploit status, detailed patch notes, or workaround text is included in the provided sources.
Mitigation direction
Identify all PROLIZ OBS deployments and current versions.
Check PROLIZ or government advisory guidance for the official remediation.
Update OBS to v26.0328 or later if applicable and vendor-supported.
Restrict OBS access to trusted networks and authorized users.
Review application logs for unusual cross-user record access.
Validation and detection
Confirm whether any OBS instance is below v26.0328.
Verify role-based access controls using approved test accounts.
Check that users cannot access records outside their authorization scope.
Review logs for abnormal access patterns involving many user or record identifiers.
Document remediation status and residual access-control risks.
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-639: 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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.