CVE-2025-6935
BaseFortify
Publication date: 2025-07-01
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 | 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-6935 is a critical SQL injection vulnerability in Campcodes Sales and Inventory System version 1.0, specifically in the file /pages/payment_add.php. The vulnerability occurs because the 'cid' parameter is not properly sanitized or validated before being used in an SQL query. This allows an attacker to inject malicious SQL code remotely without authentication, potentially altering the SQL query's logic to perform unauthorized database operations such as retrieving, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact the confidentiality, integrity, and availability of your system. An attacker can exploit it remotely to gain unauthorized access to the database, leak sensitive information, tamper with data, gain full system control, or disrupt services. This compromises 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 checking for the presence of the vulnerable endpoint '/pages/payment_add.php' and testing the 'cid' parameter for SQL injection. One method is to use Google Dorking with the query 'inurl:pages/payment_add.php' to identify potentially vulnerable targets. Additionally, a proof-of-concept exploit involves sending a crafted POST request to '/pages/payment_add.php' with a payload such as: cid=-1' or (updatexml(1,concat(0x7e,(select database())),1))# which attempts to extract the database name via SQL injection. Network or system detection can involve monitoring for such suspicious POST requests targeting the 'cid' parameter or scanning the web application endpoints for this vulnerable script. [2, 3]
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) Enforce strict input validation and filtering on the 'cid' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts for routine database operations. 4) Conduct regular security audits of code and systems to identify and remediate vulnerabilities promptly. If possible, replace the affected component with an alternative product as no known mitigations are documented. Monitoring and blocking suspicious requests targeting '/pages/payment_add.php' can also help reduce risk. [2, 3]