CVE-2025-5971
BaseFortify
Publication date: 2025-06-10
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 | school_fees_payment_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-5971 is a critical SQL injection vulnerability in the School Fees Payment System version 1.0, specifically in the /ajx.php file. It occurs because the input parameter "name_startsWith" is not properly validated or sanitized, allowing attackers to inject malicious SQL code into database queries. This can lead to unauthorized access to the database, enabling attackers to read, modify, or delete sensitive data remotely without authentication. [1, 2, 3, 4]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, data manipulation, deletion of records, and potential full system compromise. Attackers can exploit this remotely to disrupt business continuity, compromise data integrity, and take control over the system, leading to significant security and operational risks. [1, 2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'name_startsWith' GET parameter in the /ajx.php file for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/ajx.php?name_startsWith=1" --risk=3 --level=5 --dbs. Additionally, manual testing can be done using time-based blind SQL injection payloads such as: name_startsWith=4') AND (SELECT SLEEP(5))-- - to observe delays, or UNION-based payloads to extract data. Vulnerable targets can also be identified using Google dorking with the query: inurl:ajx.php. [2, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'name_startsWith' parameter to ensure it conforms to expected formats. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. Additionally, consider replacing the affected software with an alternative product if possible. [2, 4]