CVE-2025-14950
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-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?
CVE-2025-14950 is a critical SQL injection vulnerability in version 1.0 of the code-projects Scholars Tracking System. It exists in the /delete_post.php file due to improper handling and insufficient sanitization of the 'id' parameter. This allows attackers to inject malicious SQL queries remotely without authentication, leading to unauthorized database access, data modification, deletion, and exposure of sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to severe impacts including unauthorized access to the database, extraction of sensitive information, modification or deletion of data, full system control by attackers, and potential disruption of service availability. The attack can be performed remotely without any authentication, making it highly dangerous. [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 /delete_post.php endpoint for SQL injection via the 'id' parameter. One method is to use sqlmap with a payload that triggers a delay to confirm injection, for example: sqlmap -u "http://<target>/ScholarsTrackingSystem_PHP/sts/delete_post.php" --data="id=1';SELECT SLEEP(5)#" --dbs. Additionally, Google dorking can be used to identify vulnerable targets by searching for "inurl:delete_post.php". [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Implement strict input validation and filtering on the 'id' parameter to reject malicious input. 3) Minimize database user permissions by avoiding high-privilege accounts for the application. 4) Conduct regular security audits to identify and fix vulnerabilities promptly. If possible, replace the affected component with an alternative product. [2, 3, 1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Scholars Tracking System allows unauthorized access, modification, and exposure of sensitive data, which can lead to violations of data protection standards such as GDPR and HIPAA. Exploitation could result in unauthorized disclosure of personal or protected health information, compromising confidentiality and integrity requirements mandated by these regulations. Therefore, this vulnerability negatively impacts compliance with common data protection standards by increasing the risk of data breaches and unauthorized data manipulation. [1, 2, 3]