dbcve.org
Lingdang CrmApplication · 51mis

CVE-2025-0461

HIGH · 7.5 CVSS v3.1 Published 2025-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 has been found in Shanghai Lingdang Information Technology Lingdang CRM up to 8.6.0.0 and classified as problematic. This vulnerability affects unknown code of the file /crm/weixinmp/index.php?userid=123&module=Users&usid=1&action=UsersAjax&minipro_const_type=1&related_module=Singin. The manipulation of the argument pathfile leads to path traversal. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

A path traversal vulnerability in Lingdang CRM allows remote attackers to access arbitrary files on the server via the pathfile parameter in the /crm/weixinmp/index.php endpoint. The vulnerability exists in the UsersAjax action where user-supplied input is not properly sanitized before being used in file operations.

MitigationRestrict or disable the vulnerable /crm/weixinmp/index.php endpoint immediately. Implement strict input validation on the pathfile parameter to disallow directory traversal sequences (../), or deploy web application firewall rules to block exploitation attempts until the vendor releases a patch.

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

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 and version
    Locate the CRM installation directory or check web application metadata for version information. Look for files like version.php, or check the application footer/admin panel for the version number.
    Affected if The installed version is 8.6.0.0 exactly, indicating the exact affected version.
  2. Verify the vulnerable endpoint exists
    Check if the file /crm/weixinmp/index.php exists in the web root directory. This endpoint handles WeChat MP (Mini Program) related functionality.
    Affected if The file /csm/weixinmp/index.php exists and is accessible via the web server.
  3. Confirm the UsersAjax action is exposed
    Access the URL /crm/weixinmp/index.php?action=UsersAjax or similar to determine if the UsersAjax action handler is enabled and responding.
    Affected if The UsersAjax action responds without authentication or returns a valid CRM response.
  4. Check for pathfile parameter acceptance
    Send a test request to the endpoint with a pathfile parameter, such as /crm/weixinmp/index.php?action=UsersAjax&pathfile=test, and observe if the application processes the parameter.
    Affected if The application accepts and processes the pathfile parameter without rejecting traversal sequences.
  5. Inspect input validation on pathfile
    Review the source code of /crm/weixinmp/index.php, specifically the UsersAjax action handler, to verify whether the pathfile parameter undergoes sanitization for directory traversal sequences (../ or ..\).
    Affected if The pathfile parameter lacks proper input validation or sanitization, allowing ../ sequences to pass through.

A defender is affected if Lingdang CRM version 8.6.0.0 is installed and the /crm/weixinmp/index.php endpoint with the UsersAjax action exposes an unvalidated pathfile parameter.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict or disable the vulnerable /crm/weixinmp/index.php endpoint immediately. Implement strict input validation on the pathfile parameter to disallow directory traversal sequences (../), or deploy web application firewall rules to block exploitation attempts until the vendor releases a patch.

Fix this in Lingdang Crm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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