dbcve.org
Data Leakage Prevention SystemApplication · Tipray

CVE-2025-11312

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 vulnerability was detected in Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 1.0. This affects the function findModulePage of the file findModulePage.do. The manipulation of the argument sort results in sql injection. The attack can be launched remotely. The exploit is now 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 · high confidence

SQL injection vulnerability in Tipray Data Leakage Prevention System 1.0 allows remote attackers to execute arbitrary SQL commands via the 'sort' parameter in the findModulePage.do endpoint. The lack of input validation or parameterized queries in the findModulePage function enables attackers to manipulate SQL queries.

MitigationImplement input validation and use parameterized queries (prepared statements) in the findModulePage function to neutralize SQL injection. Since the vendor has not responded to disclosure, consider network isolation and WAF rules as temporary mitigations while developing a permanent code fix or evaluating alternative solutions.

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. Identify Tipray Data Leakage Prevention System version
    Locate the product installation directory or check the web application's version information (often in about pages, footer, or admin panels). Compare the installed version against the affected version 1.0.
    Affected if The installed version is exactly 1.0
  2. Confirm findModulePage.do endpoint exists
    Access the application's web interface and attempt to reach /findModulePage.do or search for this endpoint in the application's sitemap or by reviewing exposed web resources.
    Affected if The endpoint responds to requests (returns HTTP 200 or application error rather than 404)
  3. Verify 'sort' parameter is accepted
    Send a GET or POST request to findModulePage.do including a 'sort' parameter with a test value (e.g., sort=test) and observe if the parameter is processed without rejection.
    Affected if The application accepts the 'sort' parameter and includes it in SQL queries without sanitizing special characters
  4. Test for SQL injection in sort parameter
    Submit a benign SQL injection test payload via the sort parameter (e.g., sort=1' OR '1'='1) and check if the application returns database-related errors, unexpected data, or behaves differently than expected.
    Affected if The application exhibits SQL error messages, data leakage, or altered query results indicating unsanitized input is being executed as SQL

You are affected if running Tipray Data Leakage Prevention System version 1.0 and the findModulePage.do endpoint with the sort parameter processes input without SQL sanitization.

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 input validation and use parameterized queries (prepared statements) in the findModulePage function to neutralize SQL injection. Since the vendor has not responded to disclosure, consider network isolation and WAF rules as temporary mitigations while developing a permanent code fix or evaluating alternative solutions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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