# CVE-2025-8219: Shanghai Lingdang Information Technology Lingdang CRM HTTP POST Request tabdetail_moduleSave_dxkp.php sql injection

> Remote attackers can exploit SQL injection in Lingdang CRM to read or modify database contents via the tabdetail_moduleSave_dxkp.php endpoint.

- **Severity:** Medium 5.3 (`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:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2025
- **Updated:** 28 Jul 2025
- **Also known as:** GHSA-x328-g537-v6wq

## What is CVE-2025-8219?

CVE-2025-8219 is a medium-severity SQL injection vulnerability in Shanghai Lingdang Information Technology Lingdang CRM, published on 27 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A 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."

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-8219?

It affects 1 product.


Products: 51mis Lingdang Crm.

## How do I fix CVE-2025-8219?

No fix has been published for CVE-2025-8219 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8219 being exploited?

There is no known exploitation of CVE-2025-8219 in the wild and no public exploit code.

## Other vulnerabilities in Shanghai Lingdang Information Technology Lingdang CRM

- [CVE-2025-5005](https://insights.sbomify.com/CVE-2025-5005/): Shanghai Lingdang Information Technology Lingdang CRM index_event.php server-side request forgery (medium 6.9)
- [CVE-2025-9140](https://insights.sbomify.com/CVE-2025-9140/): Shanghai Lingdang Information Technology Lingdang CRM tabdetail_moduleSave.php sql injection (medium 5.3)
- [CVE-2025-8908](https://insights.sbomify.com/CVE-2025-8908/): Shanghai Lingdang Information Technology Lingdang CRM event.php sql injection (medium 5.3)
- [CVE-2025-8345](https://insights.sbomify.com/CVE-2025-8345/): Shanghai Lingdang Information Technology Lingdang CRM yunzhijiaApi.php delete_user sql injection (medium 5.3)
- [CVE-2025-0461](https://insights.sbomify.com/CVE-2025-0461/): Shanghai Lingdang Information Technology Lingdang CRM index.php path traversal (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8219 and fix it if it is affected.

What it is: CVE-2025-8219 is a medium-severity SQL injection vulnerability in Shanghai Lingdang Information Technology Lingdang CRM, published on 27 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8219 in the wild and no public exploit code.

Affected product: Shanghai Lingdang Information Technology Lingdang CRM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8219/ (Markdown: https://insights.sbomify.com/CVE-2025-8219/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8219
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8219
- OSV: https://osv.dev/vulnerability/CVE-2025-8219

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8219/
Summaries are generated and may contain mistakes; the official description above is the record.