CVE-2025-9140: Shanghai Lingdang Information Technology Lingdang CRM · SQL Injection
Affects Shanghai Lingdang Information Technology Lingdang CRMSource CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
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
Timeline
CVE ID reserved
by VulDB
, 8 hours before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 16 minutes after disclosure
First Exploit-DB entry (opens in a new tab)
Lingdang CRM 8.6.4.7 - SQL Injection
, 7 days after disclosure
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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Shanghai Lingdang Information Technology Lingdang CRM | Affected
| Fixed in– |
AI-suggested
European organizations should immediately assess their Lingdang CRM deployments to identify affected versions. The primary mitigation is to upgrade all affected Lingdang CRM instances to version 8.6.5.4 or later, where the vulnerability has been patched through parameterized queries and input sanitization. Until upgrades can be applied, organizations should implement web application firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the 'getvaluestring' parameter. Network segmentation should be enforced to restrict external access to the CRM system, limiting exposure to trusted internal networks or VPN users only. Regular security audits and code reviews should be conducted to identify any other injection points. Additionally, monitoring and logging of database queries and web application logs should be enhanced to detect anomalous activities indicative of exploitation attempts. Backup procedures must be verified to ensure rapid recovery in case of data compromise.
Description
A vulnerability was identified in Shanghai Lingdang Information Technology Lingdang CRM up to 8.6.4.7. Affected by this issue is some unknown functionality of the file /crm/crmapi/erp/tabdetail_moduleSave.php. The manipulation of the argument getvaluestring leads to sql injection. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. Upgrading to version 8.6.5.4 can resolve this issue. The affected component should be upgraded. The vendor explains: "All SQL injection vectors were patched via parameterized queries and input sanitization in v8.6.5+."