dbcve.org
Prison Management SystemApplication · Prison Management System Project

CVE-2022-2017

HIGH · 7.2 CVSS v3.1 Published 2022-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
A vulnerability was found in SourceCodester Prison Management System 1.0. It has been rated as critical. This issue affects some unknown processing of the file /pms/admin/visits/view_visit.php of the component Visit Handler. The manipulation of the argument id with the input 2%27and%201=2%20union%20select%201,2,3,4,5,6,7,user(),database()--+ leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

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

SQL injection vulnerability in SourceCodester Prison Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the 'id' parameter in /pms/admin/visits/view_visit.php. The vulnerable component is the Visit Handler, where user-supplied input is directly concatenated into SQL queries without proper sanitization or parameterized statements.

MitigationReplace direct SQL string concatenation with prepared statements/parameterized queries in view_visit.php, implement strict input validation on the id parameter, and apply any vendor security patches. If no patch exists, consider restricting network access to the admin panel or removing the affected component until proper remediation.

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
Prison Management SystemApplication
Affected:= 1.0

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm Prison Management System installation
    Locate the web application files and identify if SourceCodester Prison Management System version 1.0 is installed. Check for the presence of the /pms/ directory structure.
    Affected if The application directory contains the Prison Management System files and the version is 1.0
  2. Locate the vulnerable PHP file
    Navigate to the /pms/admin/visits/ directory and verify that view_visit.php exists.
    Affected if The file /pms/admin/visits/view_visit.php is present on the server
  3. Inspect the SQL query implementation
    Open view_visit.php and examine how the 'id' parameter is handled in SQL queries. Look for direct string concatenation of the 'id' parameter into SQL statements without using prepared statements or parameter binding.
    Affected if The 'id' parameter is directly concatenated into SQL queries without sanitization or parameterized queries
  4. Verify the Visit Handler component is accessible
    Confirm that the web server serves the /pms/admin/visits/view_visit.php endpoint and it is reachable via HTTP/HTTPS requests.
    Affected if The vulnerable endpoint is accessible over the network to unauthenticated or authenticated users
  5. Check for input validation on the id parameter
    Examine the code for any input validation, sanitization, or type checking applied to the 'id' parameter before it is used in SQL queries.
    Affected if No input validation or sanitization is performed on the 'id' parameter before SQL execution

The environment is affected if Prison Management System 1.0 is installed, the file view_visit.php exists, and the 'id' parameter is used in direct SQL concatenation without prepared statements or 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace direct SQL string concatenation with prepared statements/parameterized queries in view_visit.php, implement strict input validation on the id parameter, and apply any vendor security patches. If no patch exists, consider restricting network access to the admin panel or removing the affected component until proper remediation.

Fix this in Prison Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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