dbcve.org
Prens Student Information SystemApplication · Algan

CVE-2022-2808

HIGH · 8.8 CVSS v3.1 Published 2022-12-02
Fix available
A fix is available. Upgrade to 2.1.11 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Algan Software Prens Student Information System allows Object Relational Mapping Injection. This issue affects Prens Student Information System: before 2.1.11.

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 · high confidence

The Prens Student Information System before version 2.1.11 contains an authorization bypass vulnerability where user-controlled input is used as a key in database operations, enabling Object Relational Mapping (ORM) injection. Attackers can manipulate ORM queries to bypass authorization checks and potentially access, modify, or delete sensitive student data.

MitigationUpgrade to Prens Student Information System version 2.1.11 or later. Additionally, implement strict input validation on all user-supplied keys and ensure proper authorization checks are performed before database operations.

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
Prens Student Information SystemApplication
Affected:< 2.1.11

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify installed version of Prens SIS
    Locate the application installation directory or check the software's built-in 'About' or version information page. Common locations include: the application root folder containing a version file, the administration panel's system information section, or the software's startup banner. Look for a file named 'version', 'VERSION', or check the application footer for version numbers.
    Affected if The installed version is below 2.1.11 (e.g., 2.1.10, 2.1.9, 2.0.x, etc.)
  2. Confirm database ORM is in use
    Examine the application's configuration files for database connection settings. Look for ORM-related configurations in files such as config.php, database.php, settings.py, or similar configuration files within the application directory. Identify if an ORM framework (like Doctrine, Hibernate, Entity Framework, or built-in ORM) is being used for database operations.
    Affected if The application uses an ORM layer for database operations and the configuration files are accessible for review
  3. Identify user-accessible database query points
    Review application source code or accessible endpoints that perform database lookups using user-supplied input as keys. Focus on areas where student records, user profiles, or administrative functions retrieve data based on identifiers provided by the user (such as student IDs, record IDs, or user keys).
    Affected if The application contains functionality where user input directly influences database query keys without apparent validation
  4. Check authentication and authorization controls
    Test the identified query endpoints by attempting to access records using modified or unexpected key values. Observe whether the application returns data without proper authorization or allows manipulation of query parameters to bypass access controls.
    Affected if The application allows unauthorized access to data through ORM query manipulation or returns data outside the expected user scope

A defender is affected if the Prens Student Information System version is below 2.1.11 and the application uses ORM-based database queries with user-supplied input as keys without proper input validation.

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 2.1.11 or later
Fixed in 2.1.11
Interim mitigation

Upgrade to Prens Student Information System version 2.1.11 or later. Additionally, implement strict input validation on all user-supplied keys and ensure proper authorization checks are performed before database operations.

Recommended fix Moderate confidence

2.1.11

  1. 1. Back up the current Prens Student Information System installation and database
  2. 2. Obtain the Prens Student Information System version 2.1.11 or later from the vendor (Algan Software)
  3. 3. Follow the vendor's standard upgrade procedure to apply version 2.1.11
  4. 4. Verify the upgrade was successful by checking the system version
  5. 5. Test that the authorization controls function correctly after upgrade
  6. 6. Monitor system logs for any unusual activity

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

Fix this in Prens Student Information System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2808 — 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-2022-2808 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