CVE-2025-14940
BaseFortify
Publication date: 2025-12-19
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 |
|---|---|---|
| fabian | scholars_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?
CVE-2025-14940 is a critical SQL injection vulnerability in the Scholars Tracking System version 1.0, specifically in the /admin/delete_user.php file. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code remotely without authentication. This flaw enables attackers to manipulate SQL queries, potentially accessing, modifying, or deleting database information. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, leakage of sensitive information, modification or deletion of data, full system control by attackers, and potential service disruptions. Since no authentication is required, attackers can remotely exploit this flaw easily, posing a severe risk to data confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the /sts/admin/delete_user.php endpoint for SQL injection. A proof-of-concept payload is `id=1';SELECT SLEEP(5)#` which can be used to check for SQL injection by observing response delays. The sqlmap tool can be used to automate detection with a command targeting the vulnerable URL and injecting the payload. Additionally, Google dorking with queries like `inurl:admin/delete_user.php` can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Implement strict input validation and filtering to ensure inputs conform to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. 4) Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, replace the affected component with an alternative product. [2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized attackers to access, modify, or delete sensitive data remotely without authentication, which can lead to breaches of confidentiality, integrity, and availability of data. Such unauthorized access and data manipulation can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and ensuring data integrity. Therefore, exploitation of this vulnerability could compromise compliance with these common standards and regulations. [1, 2, 3]