CVE-2025-14527
BaseFortify
Publication date: 2025-12-11
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized access, modification, and leakage of sensitive data due to SQL injection, which can lead to violations of data protection regulations such as GDPR and HIPAA. Exploitation risks compromising confidentiality, integrity, and availability of data, potentially resulting in non-compliance with these standards that require safeguarding personal and sensitive information. Therefore, failure to remediate this vulnerability could lead to regulatory penalties and legal consequences. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized access, modification, and leakage of sensitive data due to SQL injection, which can lead to breaches of confidentiality, integrity, and availability. Such breaches can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information. Therefore, if exploited, this vulnerability could cause violations of these standards by exposing or compromising protected data. [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 'book_id' parameter in the /view_book.php file for SQL injection using various techniques such as Boolean-based blind injection, error-based injection, time-based blind injection, and UNION-based injection. Tools like sqlmap can be used to automate detection and confirm the vulnerability. Example commands include using sqlmap with the URL containing the vulnerable parameter, e.g., `sqlmap -u "http://target/view_book.php?book_id=1" --batch --dbs`. Manual payloads for testing include: Boolean-based: `book_id=1' AND 6500=6500 AND 'ulZa'='ulZa'`; Error-based: `book_id=1' OR (SELECT 7850 FROM(SELECT COUNT(*),CONCAT(0x716b6b7171,(SELECT (ELT(7850=7850,1))),0x717a717671,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) AND 'jpcu'='jpcu'`; Time-based: `book_id=1' AND (SELECT 6312 FROM (SELECT(SLEEP(5)))mjXZ) AND 'iuQN'='iuQN'`. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'book_id' parameter to ensure it conforms to expected formats, and minimizing database user privileges to only what is necessary, avoiding high-privilege accounts such as root or admin. Additionally, conducting regular security audits to detect and remediate vulnerabilities promptly is recommended. If possible, replacing the affected software with an alternative product is suggested as no known countermeasures or patches are currently reported. [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 'book_id' parameter in the /view_book.php file for SQL injection flaws. Commands using sqlmap can be employed to automate detection, for example: sqlmap -u "http://target/view_book.php?book_id=1" --batch. Manual testing can include injecting payloads such as '1' AND 1=1 -- or time-based payloads like '1' AND SLEEP(5) -- to observe response delays or errors. Additionally, Google Dorking with queries like inurl:view_book.php can help identify vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'book_id' parameter, and minimizing database user privileges to the least necessary permissions, avoiding high-privilege accounts. Regular security audits should be conducted to detect and remediate vulnerabilities promptly. If possible, replacing the affected software with a secure alternative is recommended as no known countermeasures are reported. [1, 2, 3]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection weakness in the Advanced Library Management System 1.0 by projectworlds. It occurs in the /view_book.php file where manipulation of the book_id argument can allow an attacker to inject malicious SQL code. This can be exploited remotely and the exploit is publicly available.
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 denial of service. Since it can be exploited remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the system's data.