CVE-2025-12237
BaseFortify
Publication date: 2025-10-27
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?
CVE-2025-12237 is a critical SQL injection vulnerability in the Advanced Library Management System version 1.0 by projectworlds. It exists in the /index.php file due to improper handling of the 'keywords' parameter, which is used directly in SQL queries without adequate validation or sanitization. This flaw allows remote attackers to inject malicious SQL code, enabling unauthorized access to the database, data leakage, data tampering, and potentially full system control without requiring authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized modification, deletion, and exposure of sensitive data stored in the database. Attackers can gain unauthorized access to confidential information, tamper with data integrity, disrupt system availability, and potentially take full control of the affected system. This poses a severe risk to system security and business continuity. [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 'keywords' parameter in POST requests to the /index.php file for SQL injection. Tools like sqlmap can be used to automate detection. Example sqlmap command: sqlmap -u "http://target/index.php" --data="keywords=12345&location=&search=search" --risk=3 --level=5. Additionally, manual testing with payloads such as 'keywords=12345' AND 7943=7943 AND 'Zeqa'='Zeqa' or time-based payloads like 'keywords=12345' RLIKE SLEEP(5) AND 'bMvB'='bMvB' can help identify the vulnerability. Google dorking with the query "inurl:index.php" can help identify potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering on the 'keywords' parameter, and minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. Regular security audits should be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected software with an alternative product is suggested as no known mitigations or countermeasures have been reported. [2, 3]