dbcve.org
Covid19 Testing Management SystemApplication · Unyasoft

CVE-2025-8989

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-15
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
A vulnerability was found in SourceCodester COVID 19 Testing Management System 1.0. This issue affects some unknown processing of the file /edit-phlebotomist.php. The manipulation of the argument mobilenumber leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.

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 COVID-19 Testing Management System 1.0's edit-phlebotomist.php file allows remote attackers to inject malicious SQL queries via the mobilenumber parameter. The lack of input sanitization or parameterized queries enables database manipulation.

MitigationImplement prepared statements/parameterized queries for all database operations in affected PHP files and apply input validation. Consider disabling the affected page until a patch is applied.

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
Covid19 Testing 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 COVID-19 Testing Management System is installed
    Locate the web application directory (commonly in /var/www/html, /www/html, or C:\inetpub\wwwroot on Windows). Look for files typical to this application such as index.php, login.php, or a folder named 'covid' or 'covid19'. If you inherited this system, check with the original developer or review any documentation for installation paths.
    Affected if The application directory contains SourceCodemonitor COVID-19 Testing Management System files
  2. Verify the application version is 1.0
    Check for a version file, readme.txt, or a configuration file that may contain version information. Common locations include a version.php file in the root directory, a changelog file, or the footer of the web interface if visible. Compare the installed version against the affected range (1.0).
    Affected if The installed version is 1.0
  3. Locate the vulnerable edit-phlebotomist.php file
    Search the web application directory for the file /edit-phlebotomist.php. This may appear as edit-phlebotomist.php in the root or within a subdirectory. Use a file search command: 'find /var/www/html -name "edit-phlebotomist.php"' on Linux or 'dir /s /b edit-phlebotomist.php' on Windows.
    Affected if The file edit-phlebotomist.php exists in the application directory
  4. Confirm the mobilenumber parameter is processed by the file
    Open edit-phlebotomist.php in a text editor and search for occurrences of 'mobilenumber'. Verify that this parameter is being used in database queries without proper sanitization or parameterized queries. Look for patterns like $_POST['mobilenumber'] or $_GET['mobilenumber'] being concatenated directly into SQL statements.
    Affected if The mobilenumber parameter is present in the file and used in unsanitized SQL queries
  5. Verify the affected page is accessible over the network
    Attempt to access the file via HTTP/HTTPS using a browser or curl command (e.g., curl -k https://yourdomain/edit-phlebotomist.php). Check if the page loads or returns a response. If the application requires authentication, note that the vulnerability may still be exploitable if the authentication can be bypassed or if an authenticated session is obtained.
    Affected if The edit-phlebotomist.php page is accessible via the web server

If the system is running SourceCodester COVID-19 Testing Management System version 1.0 and the edit-phlebotomist.php file is present and accessible, the environment is likely affected by CVE-2025-8989.

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

Implement prepared statements/parameterized queries for all database operations in affected PHP files and apply input validation. Consider disabling the affected page until a patch is applied.

Fix this in Covid19 Testing Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA1.0 h
12.0 hours of engineering $2,110
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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