CVE-2025-10830
BaseFortify
Publication date: 2025-09-23
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?
This vulnerability is a SQL injection flaw in Campcodes Computer Sales and Inventory System version 1.0, specifically in the file /pages/inv_edit1.php. It occurs because the 'idd' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially accessing, modifying, or deleting database information, and possibly compromising the entire system or disrupting services. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, leakage of sensitive data, modification or deletion of data, and potentially full system compromise or service disruption. Since the attack can be performed remotely without authentication, it poses a significant security risk to the affected system and its data integrity and availability. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively impact compliance with standards such as GDPR and HIPAA because it can lead to unauthorized access and leakage of sensitive personal or health-related data. Such data breaches violate the confidentiality and integrity requirements mandated by these regulations, potentially resulting in legal penalties and loss of trust. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the vulnerable parameter `idd` in the file `/pages/inv_edit1.php` using SQL injection techniques such as boolean-based blind, error-based, and time-based blind methods. Tools like sqlmap can be used to automate detection and exploitation attempts. Example commands with sqlmap include targeting the URL with the vulnerable parameter, e.g., `sqlmap -u "http://target.com/pages/inv_edit1.php?idd=1" --dbs` to enumerate databases and confirm the vulnerability. [1]
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 inputs conform to expected formats. 3) Minimizing database user permissions by avoiding the use of high-privilege accounts for routine database operations. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. [1]