CVE-2025-8926
BaseFortify
Publication date: 2025-08-13
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unyasoft | covid19_testing_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a critical SQL injection flaw in the SourceCodester COVID 19 Testing Management System version 1.0, specifically in the /login.php file. It occurs because the 'username' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can be exploited remotely without authentication to manipulate database queries, potentially leading to unauthorized access, data leakage, data modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and potential service disruption. Attackers can retrieve sensitive information, modify or delete data, and disrupt business continuity. The attack can be performed remotely without authentication, making it a severe security risk. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in /login.php can be detected by testing the 'username' parameter for SQL injection flaws. You can use tools like sqlmap to automate detection. For example, run a command like: sqlmap -u "http://targetsite/login.php" --data="username=admin&password=any" --risk=3 --level=5 --batch. Additionally, manual testing can be done using payloads such as 'admin' AND 1=1-- or time-based injections like 'admin' AND SLEEP(5)-- to observe response delays or errors indicating injection. Google dorking with queries like inurl:login.php can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameterized queries to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'username' parameter to ensure only expected input formats are accepted. 3) Minimize database user privileges used by the application to reduce impact if exploited. 4) Consider replacing the affected software with a secure alternative. 5) Conduct regular security audits to detect and remediate vulnerabilities promptly. [1, 2, 3]