dbcve.org
Student Affairs Information SystemApplication · Prolizyazilim

CVE-2024-8261

HIGH · 7.5 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to 24.0927 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authorization Bypass Through User-Controlled Key vulnerability in Proliz Software OBS allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects OBS: before 24.0927.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The OBS software contains an authorization bypass vulnerability where an attacker can manipulate a user-controlled key to bypass access control checks. This allows exploiting incorrectly configured access control security levels, potentially enabling unauthorized access to functionality or data that should be restricted.

MitigationUpgrade OBS to version 24.0927 or later to obtain the security patch. If immediate patching is not possible, review and restrict user-controlled input used in authorization decisions and ensure access control security levels are properly configured.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Student Affairs Information SystemApplication
Affected:< 24.0927

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OBS installation version
    Locate the installed version of the Prolizyazilim Student Affairs Information System (OBS) through the software's about panel, version information page, or system administration interface. If OBS is web-based, check the application header, footer, or admin dashboard for the version number.
    Affected if The installed version is lower than 24.0927 (for example, 24.0820, 24.0600, or any version prior to 24.0927).
  2. Review access control security level configuration
    Access the OBS administrative or security configuration panel. Locate the settings controlling access control security levels. Inspect whether security levels are set to enforce proper authorization checks or if they allow override conditions.
    Affected if Access control security levels are set to a permissive or misconfigured state that permits bypass conditions.
  3. Inspect authorization logic for user-controlled parameters
    Examine the OBS application code or configuration files that handle authorization decisions. Look for instances where user-supplied input (such as keys, tokens, or parameters) directly influences access control validation without proper validation.
    Affected if User-controlled parameters are used in authorization decisions without sufficient validation or sanitization, allowing manipulation to bypass access checks.

A user is affected if their OBS installation version is below 24.0927 AND the access control security levels are incorrectly configured or allow user-controlled input to bypass authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 24.0927 or later
Fixed in 24.0927
Interim mitigation

Upgrade OBS to version 24.0927 or later to obtain the security patch. If immediate patching is not possible, review and restrict user-controlled input used in authorization decisions and ensure access control security levels are properly configured.

Recommended fix High confidence

OBS version 24.0927 or later

  1. Contact Proliz Software to obtain the updated OBS (Student Affairs Information System) version 24.0927 or later
  2. Test the new version in a non-production environment to verify the authorization bypass is resolved
  3. Plan a maintenance window for production deployment
  4. Deploy the updated version 24.0927 or later to production environment
  5. Verify that the fix resolves the authorization bypass (IDOR) vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Student Affairs Information System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8261 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-8261 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data