CVE-2025-6132
BaseFortify
Publication date: 2025-06-16
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 |
|---|---|---|
| chanjet | chanjet_crm | 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-6132 is a critical SQL injection vulnerability in Chanjet CRM version 1.0, specifically in the file /sysconfig/departmentsetting.php. It occurs because the 'gblOrgID' 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 executing arbitrary SQL commands on the database. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to view, modify, or delete sensitive data. It can also result in full system control or service disruption. Since no authentication is required, attackers can remotely exploit this flaw, compromising the confidentiality, integrity, and availability of the affected system. [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 /sysconfig/departmentsetting.php endpoint for SQL injection on the gblOrgID parameter. One common method is to use sqlmap with a URL like: http://<target>/sysconfig/departmentsetting.php?id=1&gblOrgID=1&DontCheckLogin=1 to check for SQL injection. Additionally, Google Dorking can be used to find potentially vulnerable targets by searching for URLs containing "inurl:sysconfig/departmentsetting.php". [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Use prepared statements with parameter binding to prevent SQL injection. 2) Implement strict input validation and filtering on the gblOrgID parameter. 3) Limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 4) Conduct regular security audits of code and systems. If possible, replace or update the affected product/component to a secure version. [2, 3, 1]