CVE-2025-10829
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?
This vulnerability is a SQL injection flaw in Campcodes Computer Sales and Inventory System version 1.0, specifically in the file /pages/sup_edit1.php. It occurs because the 'id' 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 compromising the system. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, data leakage, data modification or deletion, and potentially full system compromise or service disruption. Attackers can use various SQL injection techniques to extract sensitive information or disrupt the service, all without needing authentication. [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 'id' parameter in the /pages/sup_edit1.php file for SQL injection using various techniques such as boolean-based blind, error-based, and time-based blind SQL injection. Example payloads include: - Boolean-based blind: id=16" RLIKE (SELECT (CASE WHEN (8040=8040) THEN 16 ELSE 0x28 END))-- - Error-based: id=16" AND GTID_SUBSET(CONCAT(0x7170767671,(SELECT (ELT(1892=1892,1))),0x7178787071),1892)-- - Time-based blind: id=16" AND (SELECT 6905 FROM (SELECT(SLEEP(5)))VZkf)-- You can also use automated tools like sqlmap to confirm the vulnerability and extract database information by targeting the vulnerable parameter. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: - Use prepared statements with parameter binding to separate SQL code from user input. - Implement strict input validation and filtering to ensure inputs conform to expected formats. - Minimize database user permissions by avoiding use of high-privilege accounts for routine operations. - Conduct regular security audits to detect and address vulnerabilities promptly. [1]