CVE-2025-11310
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-11310 is a SQL Injection vulnerability in the Tipray Data Leakage Prevention System version 1.0, specifically in the function findFileServerPage within the file findFileServerPage.do. The vulnerability arises from improper handling of the 'sort' argument, allowing an attacker to inject malicious SQL code remotely without authentication. This can lead to unauthorized access or manipulation of the system's database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your data managed by the Tipray Data Leakage Prevention System. An attacker can remotely exploit the SQL Injection flaw to access, modify, or delete sensitive information, potentially disrupting business operations and exposing confidential data. [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 'findFileServerPage.do' interface for SQL injection via the 'sort' parameter. You can use tools like curl or sqlmap to send crafted requests to the endpoint and observe if SQL injection is possible. For example, using curl: curl -v "http://<target>/findFileServerPage.do?sort=' OR '1'='1" to check for SQL injection responses. Alternatively, sqlmap can be used to automate detection: sqlmap -u "http://<target>/findFileServerPage.do?sort=test" --risk=3 --level=5. Monitoring network traffic for unusual or malformed requests targeting this endpoint may also help detect exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the affected 'findFileServerPage.do' interface, such as applying network-level controls or firewall rules to limit exposure. Since no official patches or mitigations are available and the vendor has not responded, consider replacing the affected product with an alternative solution. Additionally, monitor logs and network traffic for exploitation attempts and apply web application firewall (WAF) rules to block SQL injection patterns targeting the 'sort' parameter. [2]