CVE-2025-14570
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-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 is a SQL injection flaw in the Advanced Library Management System 1.0 by projectworlds. It occurs due to improper handling of the admin_id argument in the /view_admin.php file, allowing an attacker to manipulate the SQL query. The attack can be performed remotely and the exploit has been published.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or deletion. Since the attack can be initiated remotely without authentication, it poses a significant risk to the confidentiality, integrity, 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 exposure and modification of sensitive information. Such security 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 common standards and regulations. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'admin_id' parameter in the /view_admin.php file for SQL injection flaws. Example payloads to test include boolean-based blind, error-based, time-based blind, and UNION query injections such as: - Boolean-based blind: admin_id=-2587' OR 5607=5607# - Error-based: admin_id=2' OR (SELECT 3768 FROM(SELECT COUNT(*),CONCAT(0x71717a7071,(SELECT (ELT(3768=3768,1))),0x716a6b7071,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- - Time-based blind: admin_id=2' AND (SELECT 8539 FROM (SELECT(SLEEP(5)))KEYH)-- - UNION query: admin_id=2' UNION ALL SELECT 6387,6387,6387,6387,6387,6387,6387,CONCAT(0x71717a7071,0x64525969636b445478546258614756746f564d774e58646a42644c435a594c6951545a6141426b79,0x716a6b7071),6387,6387,6387,6387,6387# You can also use automated tools like sqlmap to test the vulnerability by running commands such as: sqlmap -u "http://target/view_admin.php?admin_id=1" --batch Additionally, attackers may identify vulnerable targets using Google Dorking with queries like: inurl:view_admin.php [1, 3]
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 use of high-privilege accounts for routine operations. - Conduct regular security audits to detect and fix vulnerabilities promptly. - Consider replacing the affected software with an alternative product if possible. These steps help prevent SQL injection by ensuring that user input cannot alter SQL commands and by limiting the potential damage if exploited. [1, 3]