dbcve.org
Prens Student Information SystemApplication · Algan

CVE-2022-2807

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-02
Fix available
A fix is available. Upgrade to 2.1.11 or later.
See remediation →
100/100
Remediation priority · Urgent
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
SQL Injection vulnerability in Algan Software Prens Student Information System allows SQL 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 · moderate confidence

SQL Injection vulnerability in the Prens Student Information System allows attackers to inject malicious SQL queries through unsanitized input. This could enable unauthorized database access, data exfiltration, modification or deletion of student records, and potentially remote code execution depending on database configuration.

MitigationUpgrade to version 2.1.11 or later which contains the security patch. As a critical SQL injection, this should be prioritized for immediate remediation and followed by a security code review to identify similar injection points.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed version of Algan Prens Student Information System
    Check the application's about page, footer, or login page for version information. Also inspect HTTP response headers or any configuration files included with the installation that may display the software version.
    Affected if The displayed version is less than 2.1.11 or no version number is visible (indicating an older unpatched release).
  2. Locate the application configuration or startup files
    Examine the web application directory for any files that contain version metadata, such as version.php, config.php, or similar configuration files that may explicitly state the software version.
    Affected if The version found in configuration files is below 2.1.11.
  3. Confirm the application handles user input through web forms
    Review the login, student search, registration, or other data entry forms that accept user input. These are the primary vectors where unsanitized SQL queries could be injected.
    Affected if The application accepts user input through web forms without visible input validation indicators (such as parameterized queries or input sanitization mechanisms).
  4. Verify database connectivity is active
    Check that the application is connected to a backend database. SQL injection requires an active database connection to execute malicious queries.
    Affected if The application successfully connects to a database and processes SQL queries based on user input.

A user is affected if the Algan Prens Student Information System version is below 2.1.11 and the application processes user-supplied input through web forms connected to a database.

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 version 2.1.11 or later which contains the security patch. As a critical SQL injection, this should be prioritized for immediate remediation and followed by a security code review to identify similar injection points.

Recommended fix Moderate confidence

2.1.11

  1. Verify current Prens Student Information System version is below 2.1.11
  2. Obtain version 2.1.11 from the vendor (Algan Software) or official distribution channels
  3. Follow vendor-provided upgrade instructions to apply version 2.1.11
  4. After upgrade, verify the SQL injection vulnerability is resolved by testing or reviewing vendor release notes
  5. Confirm the system is running version 2.1.11 or later

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

Fix this in Prens Student Information System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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