dbcve.org
Le YanApplication · Le Show

CVE-2025-3708

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-02
Fix available
A fix is available. Upgrade to after 3.2.25 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
Le-show medical practice management system from Le-yan has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read, modify, and delete database contents.

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

Le-show medical practice management system from Le-yan contains an unauthenticated SQL injection vulnerability allowing remote attackers to inject arbitrary SQL commands. The vulnerability permits reading, modifying, and deleting database contents without any authentication credentials, indicating direct exposure of database query input to user-supplied data.

MitigationImplement parameterized queries or prepared statements for all database operations, apply input validation and sanitization, and restrict database user privileges to minimum necessary. Consider deploying a WAF as a compensating control while remediation is underway.

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
Le YanApplication
Affected:<= 3.2.25

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. Identify the installed Le Show Le Yan version
    Access the application admin panel or check the software's about/version page. If unavailable, examine the application's main DLL, executable, or configuration file for a version string. Compare this version number against the affected range: any version <= 3.2.25 is potentially vulnerable.
    Affected if The installed version is 3.2.25 or any earlier version.
  2. Verify the application is network accessible
    Confirm the Le Show Le Yan web interface is reachable over HTTP/HTTPS from your network or the internet. Since this is an unauthenticated SQL injection, the vulnerable endpoint is accessible without any login credentials.
    Affected if The application is externally accessible without authentication and the version is <= 3.2.25.
  3. Test for SQL injection error exposure
    Submit a simple SQL special character such as a single quote (') in any publicly accessible input field (login, search, patient lookup, or form parameters). Observe whether the application returns a database syntax error message.
    Affected if Database error messages are displayed in the response, indicating unsanitized input is passed to database queries.
  4. Inspect web server access logs for SQL injection patterns
    Review web server (IIS, Apache, or nginx) access logs for requests containing SQL keywords (UNION, SELECT, INSERT, DELETE) or characters like quotes, OR 1=1, or comment sequences (--, /*) in URL parameters. Filter logs for the application endpoint.
    Affected if Suspicious SQL-like patterns appear in logs targeting the Le Show application without prior authentication.
  5. Check database user privileges
    Examine the database user account used by the Le Show application. Determine whether this account has excessive privileges beyond read-only operations (such as DROP, DELETE, or administrative functions).
    Affected if The application database user has elevated privileges that could allow an attacker to read, modify, or delete arbitrary data.

You are affected if the installed Le Show Le Yan version is 3.2.25 or any earlier version, the application is network-accessible, and user-supplied input can trigger SQL errors or be injected into database queries.

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
Upgrade available Upgrade to a release after 3.2.25
Interim mitigation

Implement parameterized queries or prepared statements for all database operations, apply input validation and sanitization, and restrict database user privileges to minimum necessary. Consider deploying a WAF as a compensating control while remediation is underway.

Fix this in Le Yan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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