dbcve.org
Lingdang CrmApplication · 51mis

CVE-2025-8908

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to after 8.6.5.4 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 was determined in Shanghai Lingdang Information Technology Lingdang CRM up to 8.6.5.4. Affected by this issue is some unknown functionality of the file crm/WeiXinApp/yunzhijia/event.php. The manipulation of the argument openid leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 8.6.5 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+."

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

Critical SQL injection vulnerability in Lingdang CRM (versions up to 8.6.5.4) allows remote attackers to execute arbitrary SQL queries via the openid parameter in the yunzhijia/event.php file.

MitigationUpgrade to version 8.6.5 or later which implements parameterized queries and input sanitization to address the SQL injection vulnerability.

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

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 Lingdang CRM files on the web server, typically in the web root directory. Look for characteristic files such as index.php, admin.php, or configuration files containing 'Lingdang', 'Lingdang CRM', or '51mis'.
    Affected if The system has Lingdang CRM (51mis Lingdang Crm) installed.
  2. Determine installed version
    Locate version information in common locations: version.php, version.txt, or check the source code for version strings like 'version' or 'ver' in configuration files or the main index.php. Compare the found version against the affected range (<= 8.6.5.4).
    Affected if The installed version is 8.6.5.4 or earlier.
  3. Check for vulnerable file presence
    Inspect the web directory for the file yunzhijia/event.php. This file should exist in the web root or application directory.
    Affected if The file yunzhijia/event.php exists on the server.
  4. Verify yunzhijia module is exposed
    Confirm the yunzhijia directory is accessible via HTTP/HTTPS requests. Attempt to access yunzhijia/event.php directly through the web browser to verify the endpoint is publicly reachable.
    Affected if The yunzhijia/event.php endpoint is accessible over the network.

If Lingdang CRM version 8.6.5.4 or earlier is installed and the yunzhijia/event.php file is accessible, the environment is affected by this SQL injection vulnerability.

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 a release after 8.6.5.4
Interim mitigation

Upgrade to version 8.6.5 or later which implements parameterized queries and input sanitization to address the SQL injection vulnerability.

Recommended fix High confidence

Lingdang CRM version 8.6.5 or later

  1. 1. Identify the current installed version of Lingdang CRM by checking the system configuration or version file.
  2. 2. If the current version is 8.6.5.4 or lower, download Lingdang CRM version 8.6.5 or later from the official vendor repository.
  3. 3. Backup the existing database and application files before performing the upgrade.
  4. 4. Apply the upgrade following the vendor's standard upgrade procedure.
  5. 5. Verify the upgrade was successful by checking the new version number.
  6. 6. Confirm the crm/WeiXinApp/yunzhijia/event.php file has been updated and that the openid parameter is now handled via parameterized queries.
Caveat Review release notes for any configuration changes or data migration requirements between versions

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

Fix this in Lingdang Crm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8908 — 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-8908 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