CVE-2025-10030
BaseFortify
Publication date: 2025-09-06
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 | grocery_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-10030 is a critical SQL injection vulnerability in Campcodes Grocery Sales and Inventory System version 1.0. It occurs in the /ajax.php?action=save_receiving endpoint due to improper validation and handling of the ID parameter and other input parameters. This flaw allows attackers to inject malicious SQL code remotely without authentication, leading to unauthorized access, data modification, deletion, or exposure of sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, and potentially full system compromise or service disruption. Attackers can manipulate SQL queries to access or modify sensitive data, disrupt business operations, and compromise system integrity and availability. Exploitation requires no authentication and can be performed remotely, increasing the risk. [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 /ajax.php?action=save_receiving endpoint for SQL injection, particularly by manipulating the 'id' parameter and other related parameters such as 'ref_no', 'supplier_id', 'inv_id[]', 'product_id[]', 'qty[]', and 'price[]'. A common detection method is to perform time-based blind SQL injection tests using payloads that invoke MySQL's SLEEP() function to confirm injection feasibility. For example, sending crafted POST requests with payloads like "id=1' OR SLEEP(5)-- " and measuring response delays can indicate vulnerability. Tools such as sqlmap can automate this detection by targeting the vulnerable endpoint and parameters. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering to ensure data conforms to expected formats, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. Additionally, conducting regular security audits to detect and remediate vulnerabilities promptly is recommended. If possible, replacing the affected product with an alternative solution should be considered due to the severity and ease of exploitation. [2, 3]