CVE-2025-6902
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-6902 is a critical SQL injection vulnerability in the Inventory Management System version 1.0, specifically in the file /php_action/editUser.php. It occurs because the 'edituserName' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially gaining unauthorized access to the database, modifying or deleting data, and exposing sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, deletion of data, full system control by attackers, and potential service disruption. Since it can be exploited remotely without authentication, attackers can manipulate the system's data integrity, confidentiality, and availability, causing significant harm to the affected system and its users. [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 '/php_action/editUser.php' endpoint for SQL injection via the 'edituserName' parameter submitted as multipart form data. A common detection method is to send a time-based blind SQL injection payload, such as using the MySQL SLEEP function, to observe delayed responses indicating injection. Additionally, Google dorking with queries like 'inurl:php_action/editUser.php' can help identify vulnerable targets. Specific commands could include using curl to send crafted multipart POST requests with payloads like "edituserName=anything' OR SLEEP(5)--" and observing response delays. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'edituserName' parameter, and minimizing database user permissions by avoiding high-privilege accounts such as 'root' or 'admin' for routine operations. Regular security audits should be conducted to detect and address vulnerabilities promptly. If possible, replacing the affected component with an alternative product is also suggested. [2, 3]