CVE-2025-14210
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 in the /delete_member.php file of projectworlds Advanced Library Management System 1.0. It occurs due to manipulation of the user_id argument, allowing an attacker to inject malicious SQL code. The attack can be performed remotely and the exploit has been publicly disclosed.
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 deletion. This can compromise the integrity and confidentiality of the system's data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This SQL injection vulnerability allows unauthorized access, data leakage, and data tampering, which can lead to violations of data protection requirements under standards like GDPR and HIPAA. Exploitation may result in exposure of personal or sensitive information, undermining confidentiality and integrity obligations mandated by these regulations. Therefore, the vulnerability negatively impacts compliance by increasing the risk of unauthorized data disclosure and manipulation. [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 'user_id' parameter in the 'delete_member.php' file for SQL injection. Example payloads include boolean-based blind, error-based, and time-based blind SQL injection techniques. You can use the sqlmap tool with high risk and level settings to confirm the vulnerability. Example payloads to test include: - Boolean-based blind: user_id=1' AND 3604=3604-- jCnE - Error-based (MySQL ≥ 5.6): user_id=1' AND GTID_SUBSET(CONCAT(0x71766a7671,(SELECT (ELT(2641=2641,1))),0x71717a7671),2641)-- vFNa - Time-based blind (MySQL ≥ 5.0.12): user_id=1' AND (SELECT 3010 FROM (SELECT(SLEEP(5)))zlBh)-- oxow Using sqlmap command example: sqlmap -u "http://target/delete_member.php?user_id=1" --risk=3 --level=5 --batch [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Use prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2. Implement strict input validation and filtering to ensure inputs conform to expected formats. 3. Minimize database user permissions, avoiding use of high-privilege accounts like root or admin for routine operations. 4. Conduct regular security audits to detect and fix vulnerabilities promptly. [1]