Skip to content
Noroxi
CVE-2025-8908· NVD / CVE Program· CNA VulDB

Shanghai Lingdang Information Technology Lingdang CRM event.php sql injection

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

LowCVSS 2.1 · v4.0—No exploit Fix available
Published
Aug 13, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 25th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

8

Monitor

Low priority for now.

CVSS
8 / 40 · 2.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · VulDB
5.3
NVD has not scored this yet; the score shown is the CNA’s.

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:P

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
51mislingdang crm

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • 51mis lingdang crmup to 8.6.5.4 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (VulDB). Independent of NVD's CPE analysis and usually ahead of it.

  • Shanghai Lingdang Information Technology Lingdang CRM

    • 8.6.5not affected
    • 8.6.5.0, 8.6.5.1, 8.6.5.2, 8.6.5.3, 8.6.5.4affected

Same product

51mis: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-5005Shanghai Lingdang Information Technology Lingdang CRM index_event.php server-side request forgery
    22Monitor
  • CVE-2025-8219Shanghai Lingdang Information Technology Lingdang CRM HTTP POST Request tabdetail_moduleSave_dxkp.php sql injection
    21Monitor
  • CVE-2025-0463Shanghai Lingdang Information Technology Lingdang CRM index.php unrestricted upload
    21Monitor
  • CVE-2025-0462Shanghai Lingdang Information Technology Lingdang CRM index.php sql injection
    21Monitor
  • CVE-2025-0461Shanghai Lingdang Information Technology Lingdang CRM index.php path traversal
    21Monitor
  • CVE-2024-11123上海灵当信息科技有限公司 Lingdang CRM pdf.php path traversal
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Shanghai Lingdang Information Technology Lingdang CRM8.6.5 · descriptionVendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-821918 days apartShanghai Lingdang Information Technology Lingdang CRM HTTP POST Request tabdetail_moduleSave_dxkp.php sql injection
    21Monitor
  • CVE-2025-0462211 days apartShanghai Lingdang Information Technology Lingdang CRM index.php sql injection
    21Monitor
  • CVE-2024-11121274 days apart上海灵当信息科技有限公司 Lingdang CRM index.php sql injection
    21Monitor
  • CVE-2025-91406 days apartShanghai Lingdang Information Technology Lingdang CRM tabdetail_moduleSave.php sql injection
    8Monitor
  • CVE-2025-834514 days apartShanghai Lingdang Information Technology Lingdang CRM yunzhijiaApi.php delete_user sql injection
    8Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

CVSS vector

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:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records