CVE-2025-6503
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-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?
CVE-2025-6503 is a critical SQL injection vulnerability in the code-projects Inventory Management System version 1.0, specifically in the file /php_action/fetchSelectedCategories.php. It occurs because the 'categoriesId' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized database access, letting attackers retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of records, potential full system compromise, and disruption of service availability. Since exploitation requires no authentication and can be done remotely, attackers can easily exploit this flaw to harm system integrity and availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by testing the 'categoriesId' parameter in the /php_action/fetchSelectedCategories.php endpoint for SQL injection. You can use tools like sqlmap to automate detection and exploitation attempts. Example sqlmap command: sqlmap -u "http://target/php_action/fetchSelectedCategories.php" --data="categoriesId=1" --risk=3 --level=5 --batch. Additionally, manual testing can be done using payloads such as 'categoriesId=1 AND 7694=7694' (Boolean-based), 'categoriesId=1 OR (SELECT ... FROM INFORMATION_SCHEMA.PLUGINS ...)' (Error-based), or time-based injections like 'categoriesId=1 AND (SELECT SLEEP(5))'. Attackers also use Google dorking with queries like inurl:php_action/fetchSelectedCategories.php to identify vulnerable targets. [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 by separating SQL code from user input. 2) Enforce strict input validation and filtering on the 'categoriesId' parameter to ensure it conforms to expected formats. 3) Minimize database user privileges by avoiding use of high-privilege accounts (e.g., root or admin) for the application's database connections. 4) Conduct regular security audits to detect and remediate vulnerabilities promptly. Since no known mitigations are documented, replacing the affected component with an alternative product is also suggested. [2, 3]