CVE-2025-6502
BaseFortify
Publication date: 2025-06-23
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-6502 is a critical SQL injection vulnerability in the Inventory Management System version 1.0, specifically in the /php_action/changePassword.php file. It occurs because the 'user_id' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database, letting attackers retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Attackers can manipulate or delete data, compromise system security, and disrupt business continuity. The attack can be performed remotely without authentication, making it highly dangerous. [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 'user_id' parameter in POST requests to the /php_action/changePassword.php endpoint for SQL injection. Tools like sqlmap can be used to automate detection by targeting the 'user_id' parameter. Additionally, Google dorking with queries such as 'inurl:php_action/changePassword.php' can help identify vulnerable targets. Example sqlmap command: sqlmap -u "http://target/php_action/changePassword.php" --data="user_id=1" -p user_id --batch --level=5 --risk=3 [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection. 2) Enforce strict input validation and filtering on the 'user_id' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conduct regular security audits to detect and address vulnerabilities promptly. If possible, replace the affected component with an alternative product. [2, 3]