CVE-2025-11314
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-11314 is a critical SQL injection vulnerability in the Tipray Data Leakage Prevention System version 1.0. It exists in the function findRolePage within the file findSingConfigPage.do. By manipulating the 'sort' argument with crafted input, an attacker can inject malicious SQL commands because the system does not properly neutralize special characters in SQL queries. This allows remote attackers to exploit the system without authentication. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your data and system. An attacker can remotely exploit the SQL injection flaw to access, modify, or delete sensitive enterprise data managed by the Tipray system. Since no authentication is required, the system is highly accessible to attackers, increasing the risk of data breaches and operational disruption. [1, 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 'findSingConfigPage.do' endpoint, specifically by manipulating the 'sort' parameter with SQL injection payloads to observe if the system is vulnerable. Since a proof-of-concept exploit is publicly available on GitHub, it can be used to verify the vulnerability. Common detection commands include using curl or similar tools to send crafted HTTP requests, for example: curl -v 'http://<target>/findSingConfigPage.do?sort=1' and then testing with SQL injection payloads such as 'sort=1 OR 1=1--' to check for SQL errors or unexpected responses indicating injection. Network intrusion detection systems can also be configured to detect suspicious SQL injection patterns targeting this endpoint. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the vulnerable 'findSingConfigPage.do' endpoint if possible, applying input validation or web application firewall (WAF) rules to block malicious SQL injection payloads targeting the 'sort' parameter, and monitoring for exploitation attempts. Since no patches or official fixes are available and the vendor has not responded, consider replacing the affected product or isolating it from critical network segments to reduce exposure. [1]