dbcve.org
Lingdang CrmApplication · 51mis

CVE-2025-8345

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to 8.6.5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability classified as critical was found in Shanghai Lingdang Information Technology Lingdang CRM up to 8.6.4.7. Affected by this vulnerability is the function delete_user of the file crm/WeiXinApp/yunzhijia/yunzhijiaApi.php. The manipulation of the argument function leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 8.6.5.2 is able to address this issue. It is recommended to upgrade the affected component.

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 confidence

SQL injection vulnerability in Lingdang CRM's delete_user function within yunzhijiaApi.php allows remote attackers to inject malicious SQL queries via the function argument. The vulnerability affects versions up to 8.6.4.7 and has a public exploit available.

MitigationUpgrade Lingdang CRM to version 8.6.5.2 or later to patch the SQL injection vulnerability. If immediate upgrade is not possible, consider restricting network access to the affected API endpoint as a temporary measure.

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
Lingdang CrmApplication
Affected:< 8.6.5.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Lingdang CRM installation
    Search for the file yunzhijiaApi.php in the web root directory or application installation path
    Affected if The file yunzhijiaApi.php exists in the web application directory structure
  2. Identify installed version
    Check the application version number through the admin interface, version file, or software metadata
    Affected if The version number is less than 8.6.5.2 (versions up to 8.6.4.7 are affected)
  3. Verify vulnerable endpoint exists
    Locate the delete_user function implementation within yunzhijiaApi.php
    Affected if The delete_user function is present in the yunzhijiaApi.php file
  4. Check API accessibility
    Determine if the yunzhijiaApi.php endpoint is accessible from the network without authentication
    Affected if The API endpoint is publicly accessible or accessible to untrusted users
  5. Review database query handling
    Examine how the delete_user function handles the function argument in SQL queries within yunzhijiaApi.php
    Affected if The function argument is directly used in SQL queries without parameterization or input sanitization

A user is affected if their Lingdang CRM version is less than 8.6.5.2 and the yunzhijiaApi.php with the delete_user function is accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.6.5.2 or later
Fixed in 8.6.5.2
Interim mitigation

Upgrade Lingdang CRM to version 8.6.5.2 or later to patch the SQL injection vulnerability. If immediate upgrade is not possible, consider restricting network access to the affected API endpoint as a temporary measure.

Recommended fix High confidence

Lingdang CRM 8.6.5.2

  1. 1. Backup the current Lingdang CRM database and all application files
  2. 2. Download Lingdang CRM version 8.6.5.2 from the official vendor (Shanghai Lingdang Information Technology)
  3. 3. Replace the existing installation files with the new version 8.6.5.2 files
  4. 4. Run any provided database migration scripts included in the upgrade package
  5. 5. Verify the upgrade was successful by logging into the CRM system
  6. 6. Test the delete_user function in crm/WeiXinApp/yunzhijia/yunzhijiaApi.php to confirm the SQL injection is patched
  7. 7. Verify that existing data and functionality remain intact
Caveat Review vendor release notes for version 8.6.5.2 to check for any breaking changes or backward compatibility issues before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lingdang Crm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8345 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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