CVE-2025-10785
BaseFortify
Publication date: 2025-09-22
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-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-10785 is a critical SQL injection vulnerability in version 1.0 of the Campcodes Grocery Sales and Inventory System, specifically in the /manage_user.php file. The vulnerability occurs because the 'id' parameter is used directly in SQL queries without proper input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data modification or deletion, full system compromise, and service disruption. [1, 2]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive data, modification or deletion of data, full compromise of the system, and disruption of services. Since exploitation does not require authentication and can be performed remotely, attackers can leverage this flaw to gain control over the application and its data, potentially causing significant operational and security damage. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameter 'id' in the /manage_user.php file for SQL injection using various techniques such as boolean-based blind injection, error-based injection, time-based blind injection, and UNION-based injection. You can use tools like sqlmap to automate detection and database enumeration. Example commands include: - Boolean-based test: Access URL with parameter id=3 AND 1183=1183 - Error-based test: id=(SELECT 7267 FROM(SELECT COUNT(*),CONCAT(0x716a717871,(SELECT (ELT(7267=7267,1))),0x71627a7a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a) - Time-based test: id=3 AND (SELECT 2906 FROM (SELECT(SLEEP(5)))eNak) - UNION-based test: id=-8483 UNION ALL SELECT NULL,CONCAT(0x716a717871,0x4f7763786d424c6e4a5a73666c7863436e4e6778675a486e70704a5a647a4b6566446f646f724a,0x71627a7a71),NULL,NULL,NULL-- - Using sqlmap with the target URL and the vulnerable parameter can confirm the vulnerability and enumerate the database. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input. - Apply strict input validation and filtering to ensure inputs conform to expected formats. - Minimize database user privileges by avoiding use of high-privilege accounts (such as root or admin) for application database connections. - Conduct regular security audits to detect and fix vulnerabilities promptly. These steps help protect system security and data integrity against exploitation of the SQL injection vulnerability. [1, 2]