CVE-2025-11311
BaseFortify
Publication date: 2025-10-06
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| tipray | data_leakage_prevention_system | 1.0 |
Helpful Resources
Exploitability
| 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-11311 is a SQL Injection vulnerability in the Tipray Data Leakage Prevention System version 1.0. It occurs in the function findTenantPage within the file findTenantPage.do, where improper handling of the 'sort' argument allows an attacker to inject malicious SQL code. This flaw enables remote attackers to execute SQL injection attacks without authentication, potentially compromising the system's security. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing remote attackers to execute SQL injection attacks that compromise the confidentiality, integrity, and availability of the affected system. An attacker could manipulate database queries to access, modify, or delete sensitive data, disrupt system operations, or escalate further attacks. The exploit is easy to perform and publicly available, increasing the risk of exploitation. [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 'findTenantPage.do' interface, specifically by manipulating the 'sort' parameter to check for SQL injection vulnerabilities. Since a proof-of-concept exploit is publicly available on GitHub, you can use SQL injection testing tools such as sqlmap targeting the URL with the 'sort' parameter. For example, you might run a command like: sqlmap -u "http://<target>/findTenantPage.do?sort=<payload>" --risk=3 --level=5 to detect SQL injection. Additionally, monitoring network traffic for unusual or malformed SQL queries targeting this endpoint may help detect exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected Tipray Data Leakage Prevention System version 1.0 with an alternative solution, as no vendor patch or countermeasure is available. Additionally, you should restrict access to the 'findTenantPage.do' interface, implement web application firewalls (WAF) to block SQL injection attempts, and monitor logs for suspicious activity. Since the vulnerability allows remote unauthenticated exploitation, network-level controls and strict input validation proxies can help reduce risk until a full replacement or patch is applied. [2]