CVE-2025-11313
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-11313 is a SQL Injection vulnerability in the Tipray Data Leakage Prevention System version 1.0. It exists in the function findRolePage within the file findRolePage.do, where improper handling of the 'sort' argument allows an attacker to inject malicious SQL code. This flaw enables attackers to manipulate backend SQL queries remotely without authentication, potentially leading to unauthorized access or modification of data within the system. [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 or modify sensitive data without authorization, potentially leading to data breaches, unauthorized data manipulation, or disruption of system operations. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusual or suspicious requests to the 'findRolePage.do' endpoint, especially those manipulating the 'sort' parameter with SQL injection payloads. Network intrusion detection systems (NIDS) or web application firewalls (WAF) can be configured to alert on such patterns. Additionally, reviewing web server logs for requests to 'findRolePage.do' containing SQL syntax or special characters in the 'sort' argument can help identify exploitation attempts. Specific commands might include using tools like curl or wget to test the endpoint with crafted inputs, or using grep to search logs for suspicious patterns. For example, a command to search logs could be: `grep 'findRolePage.do' /var/log/httpd/access_log | grep -E 'sort=.*(\'|--|;|\bOR\b|\bAND\b)'`. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or blocking access to the vulnerable 'findRolePage.do' endpoint to prevent exploitation. Since no patches or vendor mitigations are available, it is recommended to replace the affected Tipray Data Leakage Prevention System version 1.0 with an alternative solution. Additionally, implementing web application firewalls (WAF) rules to detect and block SQL injection attempts targeting the 'sort' parameter can reduce risk. Monitoring and alerting on suspicious activity related to this endpoint is also advised. [2]