Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14189: SQL Injection in Chanjet CRM

0
Medium
VulnerabilityCVE-2025-14189cvecve-2025-14189
Published: Sun Dec 07 2025 (12/07/2025, 11:32:05 UTC)
Source: CVE Database V5
Vendor/Project: Chanjet
Product: CRM

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.

AI-Powered Analysis

AILast updated: 12/07/2025, 11:58:29 UTC

Technical Analysis

CVE-2025-14189 identifies a SQL injection vulnerability in Chanjet CRM, specifically in the /tools/jxf_dump_table_demo.php script. The vulnerability arises from insufficient input validation of the gblOrgID parameter, which an attacker can manipulate to inject arbitrary SQL commands remotely without requiring authentication or user interaction. This injection flaw can be exploited to read, modify, or delete sensitive CRM data stored in the backend database, potentially compromising the confidentiality, integrity, and availability of organizational data. The vulnerability affects Chanjet CRM versions up to 20251121. The exploit code has been publicly disclosed, increasing the risk of exploitation, although no active attacks have been reported. The vendor has not issued a patch or responded to disclosure attempts, leaving users exposed. The CVSS 4.0 base score is 6.9 (medium), reflecting the network attack vector, low complexity, no privileges or user interaction needed, but limited impact on confidentiality, integrity, and availability. The vulnerability does not require authentication, making it accessible to remote attackers. Given the critical role CRM systems play in managing customer and business data, exploitation could lead to significant operational and reputational damage. Organizations should urgently assess exposure and implement compensating controls until a vendor patch is available.

Potential Impact

For European organizations, exploitation of this SQL injection vulnerability could lead to unauthorized access to sensitive customer and business data managed within Chanjet CRM. This may result in data breaches, loss of customer trust, regulatory non-compliance (e.g., GDPR violations), and potential financial penalties. Integrity of CRM data could be compromised, affecting business operations, sales processes, and decision-making. Availability of the CRM system might also be impacted if attackers manipulate or delete critical data. The lack of vendor response and patch availability increases the risk exposure period. Organizations in sectors heavily reliant on CRM data, such as finance, retail, and manufacturing, may face operational disruptions. Furthermore, public disclosure of exploit code raises the likelihood of opportunistic attacks targeting unpatched systems across Europe. The impact is heightened in countries with significant Chanjet CRM market penetration or where critical infrastructure and sensitive industries utilize this software.

Mitigation Recommendations

1. Immediately restrict access to the /tools/jxf_dump_table_demo.php endpoint via network segmentation or firewall rules to limit exposure to trusted IPs only. 2. Deploy a web application firewall (WAF) with custom rules to detect and block SQL injection attempts targeting the gblOrgID parameter. 3. Conduct thorough input validation and sanitization on all user-supplied parameters, especially gblOrgID, to prevent injection attacks. 4. Monitor database logs and application logs for unusual queries or error messages indicative of exploitation attempts. 5. If possible, disable or remove the vulnerable script if it is not essential to business operations. 6. Engage with Chanjet vendor support channels persistently to obtain patches or official guidance. 7. Prepare incident response plans to quickly address potential breaches stemming from this vulnerability. 8. Consider deploying database activity monitoring tools to detect anomalous access patterns. 9. Educate IT and security teams about this vulnerability and the importance of rapid mitigation. 10. Plan for a comprehensive patch management process once a vendor fix is released.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-06T14:17:48.442Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6935691437e7cb8c9be15eec

Added to database: 12/7/2025, 11:46:28 AM

Last enriched: 12/7/2025, 11:58:29 AM

Last updated: 12/8/2025, 2:04:11 AM

Views: 19

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats