CVE-2025-10416
BaseFortify
Publication date: 2025-09-15
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-10416 is a critical SQL injection vulnerability in Campcodes Grocery Sales and Inventory System version 1.0. It exists in the /ajax.php?action=delete_supplier endpoint due to improper validation and sanitization of the 'id' parameter. This flaw allows attackers to inject malicious SQL code remotely without authentication, leading to unauthorized database access, data modification, deletion, or exposure of sensitive information. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow attackers to gain unauthorized access to the database, extract sensitive information, modify or delete data, disrupt services, and potentially take full control of the affected system. This poses significant risks to system security, data integrity, and business continuity. [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=delete_supplier endpoint for SQL injection via the 'id' parameter. A proof-of-concept involves sending crafted POST requests with SQL injection payloads, such as boolean-based blind SQL injection payloads. For example, using sqlmap to test the endpoint can help detect the vulnerability automatically. A sample payload is: id=(SELECT (CASE WHEN (2741=2741) THEN 1 ELSE (SELECT 9394 UNION SELECT 7184) END)). Using sqlmap command: sqlmap -u "http://target/ajax.php?action=delete_supplier" --data="id=1" --method=POST -p id --batch [2]
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 'id' parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Additionally, conducting regular security audits to detect and address vulnerabilities promptly is recommended. If possible, consider replacing the affected product or applying patches once available. [2]