CVE-2025-10445
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-10445 is a critical SQL injection vulnerability in Campcodes Computer Sales and Inventory System version 1.0. It occurs in the file /pages/us_transac.php when accessed with the parameter action=add. The vulnerability arises from improper validation and sanitization of the 'username' parameter, allowing attackers to inject malicious SQL code. This can lead to unauthorized database access, enabling attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to the database, data leakage, data modification or deletion, and potentially full system compromise or service disruption. Since it can be exploited remotely without authentication and public exploits exist, attackers can manipulate or destroy critical business data, 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 vulnerability can be detected by testing the vulnerable parameter 'username' in the URL /pages/us_transac.php?action=add for SQL injection. A proof-of-concept payload uses a time-based blind SQL injection technique, for example: empid=4&username=123' AND (SELECT 3619 FROM (SELECT(SLEEP(5)))bpYc) AND 'hRSo'='hRSo&password=123, which causes a delay in the database response if vulnerable. Tools like sqlmap can be used to automate detection by targeting this parameter and URL. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to separate SQL code from user input. 2) Implement strict input validation and filtering to ensure data conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. If possible, consider replacing the affected product with an alternative solution. [2, 3]