CVE-2025-14212
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-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 flaw in the Advanced Library Management System 1.0 by projectworlds. It exists in the /member_search.php file where manipulation of the 'roll_number' argument can allow an attacker to execute unauthorized SQL commands. The attack can be performed remotely and an exploit has already been published.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute arbitrary SQL commands on the database, potentially leading to unauthorized data access, data modification, or data deletion. This can compromise the confidentiality, integrity, and availability of the system's data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'roll_number' POST parameter in the /member_search.php file for SQL injection flaws. Tools like sqlmap can be used to automate detection. Example payloads include error-based injection using MySQL's GTID_SUBSET function and time-based blind injection using MySQL's SLEEP function. A sample sqlmap command to test the vulnerability is: sqlmap -u "http://target/member_search.php" --data="roll_number=1001" --risk=3 --level=5 --technique=BEUSTQ. Additionally, Google dorking with the query "inurl:member_search.php" can help identify vulnerable targets. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Enforcing strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimizing database user privileges by avoiding use of high-privilege accounts (e.g., root or admin) for application database connections. 4) Conducting regular security audits to detect and address vulnerabilities promptly. If possible, consider replacing the affected software with an alternative product. [1, 2, 3]