CVE-2025-11312
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-06

Last updated on: 2026-04-29

Assigner: VulDB

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-06
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-10-06
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
tipray data_leakage_prevention_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-11312 is a SQL Injection vulnerability in version 1.0 of the Tipray Data Leakage Prevention System by 厦门天锐科技股份有限公司. It affects the function findModulePage in the file findModulePage.do, where improper handling of the 'sort' argument allows an attacker to inject malicious SQL code. This flaw enables remote, unauthenticated attackers to manipulate the system's database queries, potentially compromising the system's security. [1, 2]


How can this vulnerability impact me? :

This vulnerability can impact you by compromising the confidentiality, integrity, and availability of the Tipray Data Leakage Prevention System. An attacker can remotely exploit the SQL Injection flaw to access, modify, or disrupt data managed by the system without authentication. This could lead to unauthorized data disclosure, data tampering, or denial of service, affecting enterprise data security and compliance management. [2]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by testing the 'findModulePage.do' endpoint for SQL injection vulnerabilities, specifically by manipulating the 'sort' parameter with SQL injection payloads. Since a public proof-of-concept exploit is available on GitHub, security testers can use SQL injection testing tools such as sqlmap or manual curl commands to inject SQL payloads into the 'sort' argument and observe the response for SQL errors or unexpected behavior. For example, a curl command to test might be: curl -v 'http://<target>/findModulePage.do?sort=1' and then try injecting SQL syntax like 'sort=1 OR 1=1--'. Automated scanners that detect SQL injection vulnerabilities can also be used against this endpoint. [2]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include discontinuing use of the affected Tipray Data Leakage Prevention System version 1.0, as no vendor patches or mitigations are available. Restricting access to the vulnerable 'findModulePage.do' endpoint via network controls such as firewalls or web application firewalls (WAF) to block malicious requests can reduce exposure. Monitoring and blocking suspicious requests targeting the 'sort' parameter may help. Ultimately, replacing the affected product with a secure alternative is recommended since the vendor has not provided any patches or mitigations. [2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart