CVE-2025-14189VulnerabilityPublished 7 Dec 2025Updated 8 Dec 2025

CVE-2025-14189: Chanjet CRM · SQL Injection

Affects Chanjet CRMSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% 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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Chanjet CRM	Affected =20251121	Fixed in–

AI-suggested

1. Immediately restrict network access to the /tools/jxf_dump_table_demo.php endpoint by implementing IP whitelisting or VPN-only access to limit exposure. 2. Deploy and configure Web Application Firewalls (WAFs) with updated SQL injection detection and prevention rules tailored to detect exploitation attempts targeting the gblOrgID parameter. 3. Conduct thorough input validation and sanitization on all user-supplied parameters, especially gblOrgID, using parameterized queries or prepared statements if possible, even as a temporary workaround. 4. Monitor database logs and application logs for unusual or suspicious SQL queries indicative of injection attempts. 5. Perform regular security audits and vulnerability scans focusing on the CRM environment to identify other potential weaknesses. 6. Develop an incident response plan specific to CRM data breaches, including notification procedures compliant with GDPR. 7. Engage with Chanjet or third-party security experts to seek or develop patches or mitigations until an official fix is released. 8. Educate IT and security teams about this vulnerability and the importance of rapid mitigation. 9. Plan for timely patch deployment once an official update becomes available, including testing in staging environments to avoid operational disruptions.

Description

A vulnerability was detected in Chanjet CRM up to 20251121. Affected is an unknown function of the file /tools/jxf_dump_table_demo.php. The manipulation of the argument gblOrgID results in sql injection. The attack may be performed from remote. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, exploitation of this SQL injection vulnerability could result in unauthorized access to sensitive customer and business data, leading to data breaches that violate GDPR and other data protection regulations. The integrity of CRM data could be compromised, affecting sales processes, customer relationship management, and decision-making. Availability of the CRM system might also be impacted if attackers execute destructive SQL commands or cause database corruption. This could disrupt business operations, cause financial losses, and damage reputations. The lack of vendor response and patch availability increases the window of exposure. Organizations in sectors such as finance, manufacturing, retail, and services that rely heavily on CRM systems for customer data management are particularly vulnerable. Additionally, regulatory scrutiny and potential fines in Europe heighten the consequences of a successful attack. The public availability of exploit code increases the likelihood of opportunistic attacks targeting unpatched systems.

Summary

CVE-2025-14189 identifies a SQL injection vulnerability in Chanjet CRM versions up to 20251121, specifically within the /tools/jxf_dump_table_demo.php script. The vulnerability arises from insufficient input validation and sanitization of the gblOrgID parameter, which is directly incorporated into SQL queries. This allows unauthenticated remote attackers to inject arbitrary SQL code, potentially enabling them to read, modify, or delete sensitive data stored in the CRM database. The vulnerability is exploitable over the network without any user interaction or privileges, increasing its risk profile. The CVSS 4.0 base score is 6.9 (medium), reflecting the ease of exploitation combined with limited scope and impact. The vendor was notified but has not issued a patch or response, and exploit code has been publicly disclosed, raising the risk of future attacks. The vulnerability threatens the confidentiality, integrity, and availability of CRM data, which often includes customer information, sales records, and business intelligence. Given the critical role of CRM systems in business operations, exploitation could lead to data breaches, loss of customer trust, and operational disruptions. No mitigations or patches are officially available, so organizations must rely on compensating controls to reduce exposure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Dec 2025, 12:29 UTC

Technical details

References

Community reviews

Related threats