CVE-2025-11109
BaseFortify
Publication date: 2025-09-28
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-11109 is a critical SQL injection vulnerability in Campcodes Computer Sales and Inventory System version 1.0. It occurs in the file /pages/us_edit.php when accessed with the parameter action=edit and an ID argument. The vulnerability arises because the ID parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code directly into database queries. This enables attackers to manipulate the database, potentially accessing, modifying, or deleting data without authorization. The attack can be performed remotely and does not require authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, modification or deletion of database records, full system compromise, and potential disruption of services. Since exploitation does not require authentication, attackers can remotely exploit the flaw to gain control over the database and possibly the entire system, threatening system security and business continuity. [1, 2, 3]
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 'id' in the URL /pages/us_edit.php?action=edit for SQL injection flaws. Common detection techniques include sending specially crafted payloads such as boolean-based tests (e.g., id=18 AND 9250=9250), error-based tests (e.g., id=18 AND GTID_SUBSET(...)), time-based tests (e.g., id=18 AND (SELECT SLEEP(5))), and UNION-based tests (e.g., id=18 UNION ALL SELECT NULL,...,CONCAT(...)). Tools like sqlmap can be used to automate detection and enumeration of the vulnerability. Example command using sqlmap: sqlmap -u "http://target/pages/us_edit.php?action=edit&id=18" --batch --dbs [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering on the 'id' parameter to ensure it only accepts expected formats (e.g., numeric values). 3) Minimize database user privileges by avoiding use of high-privilege accounts such as root or admin for the application database connection. 4) Conduct regular security audits and code reviews to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected product with a secure alternative. [1, 2]