dbcve.org
Patients Waiting Area Queue Management SystemApplication · Pamzey

CVE-2025-64081

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 /php/api_patient_schedule.php in SourceCodester Patients Waiting Area Queue Management System v1 allows attackers to execute arbitrary SQL commands via the appointmentID parameter.

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 the appointmentID parameter of /php/api_patient_schedule.php in SourceCodester Patients Waiting Area Queue Management System v1 allows unauthenticated remote attackers to inject arbitrary SQL commands, potentially leading to data exfiltration, modification, or complete database compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in api_patient_schedule.php, validate and sanitize all user inputs, and apply vendor patches if available. Consider implementing Web Application Firewall (WAF) rules as an interim measure.

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
Patients Waiting Area Queue 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
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. Confirm the affected product is installed
    Identify if Pamzey Patients Waiting Area Queue Management System is deployed on the server. Look for the application directory and check for files like index.php or login pages that indicate this specific queue management system.
    Affected if The application is Pamzey Patients Waiting Area Queue Management System version 1.0
  2. Verify the vulnerable API file exists
    Check if the file /php/api_patient_schedule.php exists in the web application directory. This file is required for the vulnerability to be present.
    Affected if The file /php/api_patient_schedule.php exists in the web root
  3. Examine the source code for vulnerable SQL query
    Review the contents of api_patient_schedule.php and locate any SQL queries that use the appointmentID parameter without proper parameterization or prepared statements. Look for patterns like 'SELECT * FROM ... WHERE appointmentID=' concatenated with user input.
    Affected if The code contains unsanitized SQL queries using the appointmentID parameter directly in the query string
  4. Test if the endpoint accepts unauthenticated requests
    Attempt to access the /php/api_patient_schedule.php endpoint without authentication headers or session cookies. Send a request with a test appointmentID value to confirm the endpoint is accessible to unauthenticated users.
    Affected if The API endpoint responds without requiring authentication
  5. Check web server and database logs for SQL injection indicators
    Review access logs for requests to api_patient_schedule.php containing SQL syntax in the appointmentID parameter (such as quotes, UNION, SELECT, or common SQL injection payloads). Also check database logs for unusual or malformed queries.
    Affected if Log entries show SQL injection attempts or suspicious patterns in the appointmentID parameter

The environment is affected if Pamzey Patients Waiting Area Queue Management System v1.0 is installed, the file /php/api_patient_schedule.php exists, and the application exposes an endpoint that accepts unauthenticated requests with the appointmentID parameter used in unsanitized SQL queries.

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 dynamic SQL queries with parameterized queries/prepared statements in api_patient_schedule.php, validate and sanitize all user inputs, and apply vendor patches if available. Consider implementing Web Application Firewall (WAF) rules as an interim measure.

Fix this in Patients Waiting Area Queue Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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