CVE-2019-25678
SQL Injection in C4G LIS 3.4 Exposes Sensitive Data
Publication date: 2026-04-05
Last updated on: 2026-04-20
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gatech | computing_for_good's_basic_laboratory_information_system | to 3.4 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-306 | The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2019-25678 is a vulnerability in C4G Basic Laboratory Information System version 3.4 that involves multiple SQL injection flaws. These flaws allow attackers who are not authenticated to inject malicious SQL code through the 'site' parameter by sending specially crafted GET requests to the users_select.php endpoint. This enables attackers to execute arbitrary SQL commands on the backend database.
As a result, attackers can extract sensitive information from the database, including patient records and system credentials.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive data such as patient records and system credentials. Because attackers can execute arbitrary SQL commands without authentication, they can potentially steal confidential information, compromise system integrity, and disrupt normal operations.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to execute arbitrary SQL commands and extract sensitive database information, including patient records and system credentials.
This exposure of sensitive patient data can lead to non-compliance with data protection regulations such as GDPR and HIPAA, which mandate the protection of personal and health information.
Failure to protect such data could result in legal penalties, loss of trust, and other regulatory consequences.