CVE-2025-11315
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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability can negatively affect compliance with standards such as GDPR and HIPAA because it risks unauthorized access and manipulation of sensitive data. Data breaches resulting from SQL injection attacks can lead to violations of data protection and privacy regulations, potentially resulting in legal penalties and loss of trust. [2]
Can you explain this vulnerability to me?
CVE-2025-11315 is a SQL Injection vulnerability in version 1.0 of the Tipray Data Leakage Prevention System. It exists in the function findUserPage within the file findUserPage.do, where manipulation of the 'sort' argument allows an attacker to inject malicious SQL code. This happens because the system constructs SQL queries using user input without properly sanitizing it. The vulnerability can be exploited remotely without authentication, enabling attackers to alter database queries. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. An attacker can remotely execute SQL injection attacks to access, modify, or delete sensitive data within the database. Since no authentication is required, exploitation is straightforward, potentially leading to data breaches, unauthorized data manipulation, or disruption of services. [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 'findUserPage.do' interface, specifically by manipulating the 'sort' argument with crafted input to check for SQL injection vulnerabilities. Since the vulnerability is a SQL injection in the 'sort' parameter, you can use tools like sqlmap or manual curl commands to test for injection. For example, a curl command to test might be: curl -v "http://<target>/findUserPage.do?sort=' OR '1'='1" to see if the response indicates SQL injection. Automated scanners or sqlmap can be used to detect this vulnerability by targeting the 'sort' parameter in the 'findUserPage.do' endpoint. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the affected 'findUserPage.do' interface to trusted networks or IPs, implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'sort' parameter, and monitoring logs for suspicious activity. Since no patches or countermeasures are currently available from the vendor, consider replacing the affected product or disabling the vulnerable functionality until a fix is available. [2]