CVE-2025-10031
7.3Campcodes · Grocery Sales and Inventory System
Campcodes Grocery Sales and Inventory System 1.0 contains a SQL injection vulnerability in the delete_sales function within ajax.php, allowing remote attackers to manipulate the ID argument.
Executive summary
A critical SQL injection vulnerability in Campcodes Grocery Sales and Inventory System 1.0 allows for remote, unauthenticated database manipulation.
Vulnerability
The application is susceptible to SQL injection via the ID parameter in the ajax.php file, which is reachable via the delete_sales action. This vulnerability requires no authentication, allowing unprivileged remote attackers to execute arbitrary SQL commands.
Business impact
The ability to perform unauthorized SQL injection attacks poses a severe risk to data integrity and confidentiality. Attackers may be able to extract sensitive information, modify database records, or potentially disrupt service availability. With a CVSS score of 7.3, this high-severity vulnerability represents a significant risk to any organization relying on this system for inventory management.
Remediation
Immediate Action: Since no official patch is currently available, administrators should immediately restrict access to the affected system or take the application offline until a vendor-supplied update is released.
Proactive Monitoring: Review web server access logs for suspicious requests targeting the ajax.php endpoint, specifically looking for unusual patterns in the ID parameter.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection attempts, specifically monitoring for malicious input within the URL query parameters.
Exploitation status
Public Exploit Available: Yes, a published proof-of-concept exists, as documented in the technical write-up provided by the vulnerability researcher.
Analyst recommendation
Given the public availability of exploit code and the lack of a verified vendor patch, organizations must treat this vulnerability with high urgency. It is recommended to implement strict network access controls or disable the vulnerable functionality entirely until official remediation can be applied. Failure to restrict access exposes the underlying database to potential compromise by unauthenticated remote actors.
Sources
Originally found and disclosed by zzb2 (VulDB User), per the CVE Program record.