Skip to main content
VulnerabilityPublished

CVE-2025-6132: Chanjet CRM · SQL Injection

Affects Chanjet CRMSource CVE Database V5

0

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubchanjet/CRMpkg:github/chanjet/CRMOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate mitigation should focus on restricting external access to the vulnerable endpoint (/sysconfig/departmentsetting.php) via network-level controls such as firewalls or web application firewalls (WAFs) configured to detect and block SQL injection patterns targeting the 'gblOrgID' parameter.
  2. Implement strict input validation and parameterized queries or prepared statements in the application code to prevent injection attacks once source code access is possible.
  3. Monitor application logs and database query logs for unusual or suspicious activity related to the 'gblOrgID' parameter or unexpected SQL queries.
  4. Conduct a thorough audit of all CRM inputs and endpoints to identify and remediate similar injection vulnerabilities.
  5. Engage with Chanjet vendor support channels to obtain or request an official patch or security update.
  6. If feasible, isolate the CRM system from direct internet exposure by placing it behind VPNs or internal networks accessible only to authorized personnel.
  7. Educate IT and security teams about this vulnerability and ensure incident response plans include steps for SQL injection detection and containment.
  8. Prepare for rapid deployment of patches once released and test updates in a controlled environment before production rollout.

Description

A vulnerability has been found in Chanjet CRM 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /sysconfig/departmentsetting.php. The manipulation of the argument gblOrgID leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…