CVE-2025-8219

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2025-07-27) is not newer than that change (2026-06-17), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 27, 2025

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Oct 11, 2026
Fix named in the CVE record.
Web page

Notion

https://www.notion.so/SQL-Injection-Vulnerability-in-Lingdang-CRM-231ac9e8711e8017ab4ee3bb5f4aab0b?source=copy_link

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 88 of 151 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 12 repeat rows among the latest 100 are merged into the row they repeat. The 63 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 20:19 UTCEG score recompute
  2. 2026-10-11 18:31 UTCEG score recompute
  3. 2026-10-11 15:05 UTCEG score recompute
  4. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 63 more
  1. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  27. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  28. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  29. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  30. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  31. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  32. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  33. 2026-08-07 16:27 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  34. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  35. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  36. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  37. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  38. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  39. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  40. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  41. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  42. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  43. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  44. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  45. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  46. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  47. 2026-07-23 03:03 UTCEG score recompute▲ 3.50
  48. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  49. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  50. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  51. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  52. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  53. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  54. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  55. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  56. 2026-07-15 01:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  57. 2026-07-13 06:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  58. 2026-07-12 05:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  59. 2026-07-11 08:27 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  60. 2026-07-09 19:10 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  61. 2026-07-08 15:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  62. 2026-07-07 13:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  63. 2026-07-06 16:27 UTCEPSS rescoreEPSS 0.4% · 29th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-8219?
CVE-2025-8219 is a critical-severity vulnerability; its CVE record was published on July 27, 2025. 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/tabdetailmoduleSavedxkp.php of the component HTTP POST Request Handler. The manipulation of the…
When was the CVE record for CVE-2025-8219 published?
The CVE record for CVE-2025-8219 was published on July 27, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2025-8219 actively exploited?
CVE-2025-8219 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-8219?
CVE-2025-8219 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-8219?
The CVE record for CVE-2025-8219 names the fix: "We strongly advise all customers to upgrade to the current version (v8.6.5.2), which includes this fix and additional security enhancements."".

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-8219

Explore →

Is Your Infrastructure Affected by CVE-2025-8219?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs