dbcve.org
Data Leakage Prevention SystemApplication · Tipray

CVE-2025-11311

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 security vulnerability has been detected in Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 1.0. The impacted element is the function findTenantPage of the file findTenantPage.do. The manipulation of the argument sort leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed publicly 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 · high confidence

SQL injection vulnerability in Tipray Data Leakage Prevention System 1.0 allows remote attackers to inject malicious SQL statements via the 'sort' parameter in the findTenantPage.do endpoint. The lack of input validation or parameterized queries in the findTenantPage function enables attackers to manipulate database queries, potentially allowing unauthorized data access, modification, or complete system compromise.

MitigationImplement immediate compensating controls such as web application firewall (WAF) rules to block SQL injection payloads in the sort parameter, and contact vendor for official patch; if no patch is available, consider network segmentation to restrict access to this endpoint and implement strict input validation at the application layer.

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
Data Leakage Prevention SystemApplication
Affected:= 1.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
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 Tipray Data Leakage Prevention System is installed
    Check your installed software inventory or application list for 'Tipray Data Leakage Prevention System'. If installed via web server, verify the web application directory contains Tipray DLP components.
    Affected if The product is not installed or has been removed entirely.
  2. Verify the installed version is exactly 1.0
    Check the product's about page, version information within the application, or installed packages for the exact version number. Compare your installed version to the affected range (= 1.0).
    Affected if Your installed version is anything other than 1.0.
  3. Determine if the web interface is accessible
    Check if the application's HTTP/HTTPS ports are open and responding. Attempt to access the login page or main interface of the Data Leakage Prevention System.
    Affected if The application web interface is not accessible from your network location.
  4. Locate the findTenantPage.do endpoint
    Review your web server logs or application directory for the presence of the findTenantPage.do file. Check if this endpoint is registered and accessible in the application's URL routing.
    Affected if The findTenantPage.do endpoint does not exist in your environment.

You are affected if Tipray Data Leakage Prevention System version 1.0 is installed and the findTenantPage.do endpoint is accessible in your environment, as the SQL injection vulnerability exists in the sort parameter of this specific endpoint.

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

Implement immediate compensating controls such as web application firewall (WAF) rules to block SQL injection payloads in the sort parameter, and contact vendor for official patch; if no patch is available, consider network segmentation to restrict access to this endpoint and implement strict input validation at the application layer.

Fix this in Data Leakage Prevention System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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