CVE-2025-14584
BaseFortify
Publication date: 2025-12-12
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 |
|---|---|---|
| angeljudesuarez | covid_tracking_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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?
This vulnerability is a SQL injection in the Admin Login component of the itsourcecode COVID Tracking System 1.0. Specifically, it occurs in an unknown function within the /admin/login.php file when the Username argument is manipulated. This allows an attacker to inject malicious SQL code remotely, potentially compromising the system.
How can this vulnerability impact me? :
The SQL injection vulnerability can allow an attacker to execute arbitrary SQL commands on the database, which may lead to unauthorized access, data leakage, data modification, or disruption of service. Since the attack can be initiated remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'username' parameter in the /admin/login.php endpoint for SQL injection flaws. A proof-of-concept involves sending a POST request with a payload such as `username=admin' AND (SELECT 4504 FROM (SELECT(SLEEP(5)))cvjm) AND 'Jlap'='Jlap` and any password, which causes a delay if the system is vulnerable. Automated tools like sqlmap can be used to test the endpoint by targeting the login URL and attempting injection attacks. Additionally, Google dorking with queries like `inurl:admin/login.php` can help identify vulnerable targets. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL logic from user input, enforcing strict input validation and filtering on the 'username' parameter, and minimizing database user privileges by avoiding the use of high-privilege accounts such as root or admin for routine operations. Conducting regular security audits to detect and remediate vulnerabilities promptly is also recommended. If possible, replacing the affected product or component is advised. [1, 3, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized access to sensitive data through SQL injection, it could potentially lead to data breaches that violate data protection regulations. Immediate remediation is recommended to protect system security and data integrity, which are critical for compliance. [1, 2, 3]