CVE-2025-8219
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 · uneditedA vulnerability was found in Shanghai Lingdang Information Technology Lingdang CRM up to 8.6.4.7. It has been rated as critical. This issue affects some unknown processing of the file /crm/crmapi/erp/tabdetail_moduleSave_dxkp.php of the component HTTP POST Request Handler. The manipulation of the argument getvaluestring leads to sql injection. The attack may be initiated remotely. Upgrading to version 8.6.5.2 is able to address this issue. It is recommended to upgrade the affected component. The vendor explains: "All SQL injection vectors were patched via parameterized queries and input sanitization in v8.6.5+. We strongly advise all customers to upgrade to the current version (v8.6.5.2), which includes this fix and additional security enhancements."
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 confidenceSQL injection vulnerability in Lingdang CRM up to v8.6.4.7 in the /crm/crmapi/erp/tabdetail_moduleSave_dxkp.php file allows remote attackers to inject malicious SQL queries via the getvaluestring parameter in HTTP POST requests. This is a critical vulnerability due to the potential for complete database compromise, including data exfiltration, modification, or administrative access.
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< 8.6.5.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Lingdang CRM installed versionCheck the application version in the software's About page, license file, or version configuration file typically found in the crm directory or a config file. Compare against the vulnerable range: versions prior to 8.6.5.2 are affected.Affected if Installed version is lower than 8.6.5.2
-
Locate vulnerable PHP endpointCheck if the file /crm/crmapi/erp/tabdetail_moduleSave_dxkp.php exists on the web server by inspecting the webroot directory structure.Affected if The vulnerable PHP file exists in the crm installation directory
-
Verify HTTP POST parameter exposureReview HTTP access logs or use a web proxy to inspect if POST requests to the vulnerable endpoint with the getvaluestring parameter are being processed by the application.Affected if The application accepts and processes the getvaluestring parameter via HTTP POST to the vulnerable endpoint
If the installed Lingdang CRM version is below 8.6.5.2 and the vulnerable PHP endpoint is accessible, the environment is likely affected by this SQL injection.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped8.6.5.2
Upgrade to Lingdang CRM version 8.6.5.2 or later, which implements parameterized queries and input sanitization to address SQL injection vectors.
8.6.5.2
- 1. Back up the current Lingdang CRM database and configuration files before proceeding with any upgrade.
- 2. Download Lingdang CRM version 8.6.5.2 from the official vendor source or authorized distribution channel.
- 3. Review the vendor's upgrade documentation for version 8.6.5.2 to understand any prerequisites or specific upgrade procedures.
- 4. Execute the upgrade process according to vendor instructions, applying the patch to all affected production and staging environments.
- 5. After upgrade completion, verify the /crm/crmapi/erp/tabdetail_moduleSave_dxkp.php endpoint is no longer vulnerable by confirming parameterized queries are in use.
- 6. Test core CRM functionality to ensure the upgrade did not introduce regressions.
- 7. Verify the application version reflects 8.6.5.2 or higher in the administration interface.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8219 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8219 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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