dbcve.org
Chanjet CrmApplication · Chanjet

CVE-2025-6132

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Chanjet CRM 1.0's /sysconfig/departmentsetting.php file. The gblOrgID parameter is vulnerable to SQL injection, allowing remote attackers to execute arbitrary SQL commands via unauthenticated HTTP requests.

MitigationApply vendor patch immediately. If unavailable, implement parameterized queries or input validation/sanitization on the gblOrgID parameter. Consider restricting network access to the affected endpoint until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Chanjet CrmApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Chanjet CRM is installed
    Inventory your web applications and identify if Chanjet CRM (or a product named Chanjet Chanjet Crm) is deployed in your environment. Check web server directories, application lists, or asset management records for this product.
    Affected if Chanjet CRM version 1.0 is present in the environment
  2. Verify the installed version is 1.0
    Locate the application version information for Chanjet CRM. Check the application About page, version file, installation manifest, or admin panel for the exact version number. Compare against the affected range: version 1.0.
    Affected if The installed version is exactly 1.0
  3. Locate the vulnerable PHP file
    Search the web root directory for the file /sysconfig/departmentsetting.php. This file should exist within the Chanjet CRM web application directory structure.
    Affected if The file /sysconfig/departmentsetting.php exists in the Chanjet CRM installation
  4. Check if the vulnerable endpoint is network accessible
    Test HTTP access to the path /sysconfig/departmentsetting.php on the server running Chanjet CRM. Use a web browser or curl command: curl -k https://<target>/sysconfig/departmentsetting.php
    Affected if The endpoint returns an HTTP response (200, 400, 500, etc.) rather than a 404 or connection refused error
  5. Verify the gblOrgID parameter is accepted
    Send a request to /sysconfig/departmentsetting.php with a test value for the gblOrgID parameter, such as: curl -k 'https://<target>/sysconfig/departmentsetting.php?gblOrgID=test'. Observe if the parameter is processed by the application.
    Affected if The application accepts and processes the gblOrgID parameter without rejecting it

A user is affected if they are running Chanjet CRM version 1.0 with the /sysconfig/departmentsetting.php endpoint accessible over the network and the gblOrgID parameter is accepted by the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch immediately. If unavailable, implement parameterized queries or input validation/sanitization on the gblOrgID parameter. Consider restricting network access to the affected endpoint until patched.

Fix this in Chanjet Crm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6132 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6132 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data