CVE-2025-7536
BaseFortify
Publication date: 2025-07-13
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-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-7536 is a critical SQL injection vulnerability in Campcodes Sales and Inventory System version 1.0, specifically in the /pages/receipt_credit.php file. The vulnerability occurs because the application improperly handles the 'sid' parameter by directly incorporating user input into SQL queries without proper sanitization or validation. This allows an attacker to inject malicious SQL code remotely, enabling unauthorized manipulation of the database. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, modification, or deletion. Attackers can exploit it remotely without authentication, potentially causing full system compromise or service disruption. The confidentiality, integrity, and availability of the system are at risk due to this flaw. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying if the /pages/receipt_credit.php endpoint is accessible and vulnerable to SQL injection via the sid parameter. One method is to perform a test injection by sending crafted HTTP requests to this endpoint with SQL payloads in the sid parameter and observing the response for SQL errors or unexpected behavior. Additionally, Google dorking can be used to find potentially vulnerable targets using queries like: inurl:pages/receipt_credit.php. For example, you can use curl or similar tools to send a test request: curl -X POST -d "sid=1' OR '1'='1" http://target.com/pages/receipt_credit.php and check for SQL error messages or abnormal responses indicating injection. Monitoring network traffic for suspicious POST requests to /pages/receipt_credit.php with unusual sid parameter values can also help detect exploitation attempts. [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 sid parameter to ensure it meets expected formats and reject malicious input. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as root or admin for routine database operations. 4) Conduct regular security audits and code reviews to detect and remediate vulnerabilities promptly. If possible, update or replace the affected software component with a patched or alternative version that addresses this vulnerability. [2, 3]