CVE-2025-10831
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-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-10831 is a critical SQL injection vulnerability in Campcodes Computer Sales and Inventory System 1.0, specifically in the file /pages/pro_edit1.php. The vulnerability arises because the prodcode parameter is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially gaining unauthorized access to the database, leaking or manipulating data, taking full control of the system, or disrupting services. [1]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, data manipulation, full system compromise, and potential disruption of services. Attackers can exploit the flaw remotely without needing authentication, which increases the risk of exploitation and can threaten business continuity and system security. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'prodcode' parameter in the /pages/pro_edit1.php file for SQL injection using techniques such as boolean-based blind, error-based, and time-based blind SQL injection. Example payloads include: - Boolean-based blind: prodcode=20191001" RLIKE (SELECT (CASE WHEN (8318=8318) THEN 20191001 ELSE 0x28 END))-- - Error-based: prodcode=20191001" AND (SELECT 1730 FROM(SELECT COUNT(*),CONCAT(0x7162787671,(SELECT (ELT(1730=1730,1))),0x716a767a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- - Time-based blind: prodcode=20191001" AND (SELECT 3512 FROM (SELECT(SLEEP(5)))NdNW)-- Additionally, the sqlmap tool can be used to automate detection and confirm the vulnerability by enumerating the database. [1]
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 permissions by avoiding high-privilege accounts for routine operations. - Conduct regular security audits to detect and fix vulnerabilities promptly. [1]