CVE-2025-14951
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-14951 is a critical SQL injection vulnerability in the Scholars Tracking System version 1.0, specifically in the /home.php file. It occurs because the 'post_content' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially executing unauthorized database operations such as data leakage, modification, deletion, or denial of service. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to remotely execute arbitrary SQL commands on your database without authentication. This can lead to unauthorized access to sensitive data, modification or deletion of data, full system compromise, and denial of service. The exploit can be used to leak confidential information, corrupt data integrity, and disrupt system 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 'post_content' POST parameter in the /home.php file for SQL injection. A practical method is to use tools like sqlmap to automate detection. For example, running a command such as `sqlmap -u "http://<target>/ScholarsTrackingSystem_PHP/sts/home.php" --data="post_content=test"` can help identify the injection point. Additionally, a proof-of-concept payload like `post_content=cute Guan Yingxin');SELECT SLEEP(5)#&post=` can be used to check for delayed responses indicating SQL injection. Network detection can also involve searching for unusual SQL error messages or delays in database response times when this parameter is used. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Applying strict input validation and filtering on the 'post_content' parameter to ensure it conforms to expected formats. 3) Minimizing database user permissions by avoiding high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected software with a secure alternative until a patch is available. [1, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized access, modification, and deletion of sensitive data through SQL injection, which can lead to breaches of confidentiality, integrity, and availability of data. Such breaches 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 cause violations of these standards and regulations. [1, 2, 3]