CVE-2025-6891
BaseFortify
Publication date: 2025-06-30
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 |
|---|---|---|
| code-projects | inventory_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-6891 is a critical SQL injection vulnerability in version 1.0 of the Inventory Management System, specifically in the file /php_action/createUser.php. The vulnerability occurs because the 'Username' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, modification or deletion of data, full system control, and potential service disruption. Attackers can exploit this flaw remotely without any login, posing significant risks 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 vulnerable endpoint /php_action/createUser.php for SQL injection in the userName parameter. A time-based blind SQL injection test can be performed by sending a specially crafted multipart/form-data POST request with a payload such as: Content-Disposition: form-data; name="userName" 11111' AND (SELECT 1489 FROM (SELECT(SLEEP(5)))RXbe) AND 'tlId'='tlId If the response is delayed by the sleep time, it confirms the vulnerability. Additionally, attackers may identify vulnerable targets using Google dorking with the query: inurl:php_action/createUser.php Commands to test this could include using curl to send the payload: curl -X POST -F "userName=11111' AND (SELECT 1489 FROM (SELECT(SLEEP(5)))RXbe) AND 'tlId'='tlId" https://targetsite.com/php_action/createUser.php Monitoring network traffic for unusual delays or suspicious POST requests to this endpoint can also help detect exploitation attempts. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements (parameterized queries) in the /php_action/createUser.php file to ensure user inputs are treated as data, preventing SQL injection. - Apply strict input validation and filtering on the userName parameter to enforce expected formats and reject malicious input. - Minimize database user permissions by avoiding use of high-privilege accounts for routine database operations. - Conduct regular security audits and code reviews to detect and fix vulnerabilities promptly. - If possible, consider replacing the affected product with a more secure alternative. These steps help prevent exploitation and reduce the risk of unauthorized database access and data compromise. [1, 2]