CVE-2025-14211
BaseFortify
Publication date: 2025-12-08
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-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?
This vulnerability exists in the Advanced Library Management System 1.0 by projectworlds. It occurs in the /delete_book.php file where manipulation of the 'book_id' argument leads to an SQL injection. This means an attacker can remotely inject malicious SQL code through the 'book_id' parameter, potentially compromising the database.
How can this vulnerability impact me? :
The vulnerability allows remote attackers to perform SQL injection via the 'book_id' parameter, which can lead to unauthorized access, modification, or deletion of data in the database. This can compromise the integrity, confidentiality, and availability of the system's data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized database access, data leakage, and data tampering, which can lead to breaches of sensitive information. Such breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access and ensuring data integrity. Therefore, exploitation of this SQL injection vulnerability could compromise compliance with these standards. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'book_id' parameter in the /delete_book.php file for SQL injection using various SQL injection techniques such as boolean-based blind, error-based, and time-based blind injections. Example payloads include: - Boolean-based blind: book_id=1' OR NOT 3450=3450-- - Error-based (MySQL >= 5.6): book_id=1' AND GTID_SUBSET(CONCAT(0x7176717171,(SELECT (ELT(7093=7093,1))),0x71766b7671),7093)-- - Time-based blind (MySQL >= 5.0.12): book_id=1' OR (SELECT 1847 FROM (SELECT(SLEEP(5)))ynLu)-- You can also use automated tools like sqlmap to confirm the vulnerability by targeting the URL with the vulnerable parameter, for example: sqlmap -u "http://target/delete_book.php?book_id=1" --batch --dbs [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Use prepared statements with parameter binding to separate SQL code from user input. - Implement strict input validation and filtering to ensure inputs conform to expected formats. - Minimize database user permissions by avoiding high-privilege accounts for routine operations. - Conduct regular security audits to detect and fix vulnerabilities promptly. These steps help protect system security and data integrity against SQL injection attacks. [1]