CVE-2025-10435
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 | computer_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-10435 is a critical SQL injection vulnerability in Campcodes Computer Sales and Inventory System version 1.0, specifically in the file /pages/cust_edit1.php. The vulnerability occurs because the 'id' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially gaining unauthorized access to the database, manipulating data, or disrupting the system. Various SQL injection techniques such as boolean-based blind, error-based, and time-based injections have been demonstrated against this parameter. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, data manipulation, deletion, and exposure of confidential information. Attackers can gain full control over the database and potentially disrupt services, leading to loss of business continuity and system integrity. Since exploitation does not require authentication and can be performed remotely, the risk is significant. [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 'id' parameter in the /pages/cust_edit1.php file for SQL injection using tools like sqlmap. Example commands include using sqlmap to target the URL with the vulnerable parameter, such as: sqlmap -u "http://target.com/ComputerSalesInventorySystem/pages/cust_edit1.php?id=1" --batch --dbs. Additionally, manual testing can involve sending crafted POST requests with SQL injection payloads targeting the 'id' parameter, including boolean-based, error-based, and time-based SQL injection techniques (e.g., using MySQL RLIKE, GTID_SUBSET, or SLEEP functions). Attackers may also use Google dorking with queries like "inurl:pages/cust_edit1.php" to identify vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input; 2) Applying strict input validation and filtering to ensure the 'id' parameter only accepts expected formats; 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine database operations; 4) Conducting regular security audits to detect and address vulnerabilities promptly. Replacement or patching of the affected software version is also recommended to fully remediate the issue. [1, 3]