CVE-2025-6311
BaseFortify
Publication date: 2025-06-20
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 |
|---|---|---|
| campcodes | sales_and_inventory_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-6311 is a critical SQL injection vulnerability in the Complete Sales and Inventory System version 1.0, specifically in the /pages/account_add.php file. The vulnerability occurs because the application directly uses the 'id' and 'amount' parameters in SQL queries without proper sanitization or validation. This allows an attacker to inject malicious SQL code remotely, enabling unauthorized manipulation of the database, such as extracting data or altering records, without requiring authentication. [1, 2, 3, 4]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, sensitive data leakage, data tampering, and potentially full system control by attackers. It can also cause service disruption and compromise the confidentiality, integrity, and availability of the sales and inventory system, posing severe risks to system security and business continuity. [3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /pages/account_add.php endpoint for SQL injection via the 'id' and 'amount' parameters. One approach is to send crafted HTTP requests with SQL injection payloads to these parameters and observe the responses for SQL errors or unexpected behavior. Additionally, Google dorking can be used to identify potentially vulnerable targets by searching for "inurl:pages/account_add.php". A proof-of-concept exploit involves sending a POST request with SQL injection payloads such as using the updatexml function to extract database information. Example command using curl to test the 'id' parameter: curl -X POST -d "id=1' OR '1'='1" https://target.com/pages/account_add.php Monitoring web server logs for suspicious input patterns or error messages related to SQL syntax errors can also help detect exploitation attempts. [3, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Implement prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection. 2. Apply strict input validation and filtering on the 'id' and 'amount' parameters to ensure they conform to expected formats. 3. Minimize database user permissions by avoiding the use of high-privilege accounts for routine database operations. 4. Conduct regular security audits and code reviews to detect and fix vulnerabilities promptly. If immediate patching is not possible, consider restricting access to the vulnerable endpoint or replacing the affected product with a secure alternative. [3]