Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-11315: SQL Injection in Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统

0
Medium
VulnerabilityCVE-2025-11315cvecve-2025-11315
Published: Mon Oct 06 2025 (10/06/2025, 02:02:05 UTC)
Source: CVE Database V5
Vendor/Project: Tipray 厦门天锐科技股份有限公司
Product: Data Leakage Prevention System 天锐数据泄露防护系统

Description

A vulnerability was found in Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 1.0. Affected by this vulnerability is the function findUserPage of the file findUserPage.do. Performing manipulation of the argument sort results in sql injection. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 10/13/2025, 11:09:33 UTC

Technical Analysis

CVE-2025-11315 identifies a SQL injection vulnerability in the Tipray Data Leakage Prevention System (version 1.0), specifically within the findUserPage.do endpoint's findUserPage function. The vulnerability arises from improper sanitization of the 'sort' parameter, which is directly used in SQL queries without adequate validation or parameterization. This allows remote attackers to inject malicious SQL code, potentially leading to unauthorized data access, data modification, or disruption of database operations. The vulnerability is exploitable remotely without authentication or user interaction, increasing its risk profile. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the network attack vector, low complexity, no privileges required, and no user interaction needed. The impact on confidentiality, integrity, and availability is rated low individually but collectively significant due to the potential for data leakage or corruption. The vendor, Tipray 厦门天锐科技股份有限公司, has not responded to vulnerability reports, and no official patches or mitigations have been released. Public exploit code has been disclosed, increasing the likelihood of exploitation attempts. The affected product is a Data Leakage Prevention system, which is critical for protecting sensitive data, making this vulnerability particularly concerning for organizations relying on it to secure their information assets.

Potential Impact

For European organizations, exploitation of this SQL injection vulnerability could lead to unauthorized access to sensitive data managed or monitored by the Tipray Data Leakage Prevention System. This may result in data breaches, exposure of confidential information, or manipulation of security controls, undermining the effectiveness of data protection strategies. The integrity of logs and monitoring data could also be compromised, impeding incident detection and response. Given that the vulnerability requires no authentication and can be exploited remotely, attackers could leverage it to gain footholds within networks or exfiltrate data without detection. Organizations in regulated industries such as finance, healthcare, and government are particularly at risk due to stringent data protection requirements under GDPR and other regulations. The lack of vendor response and absence of patches increase the window of exposure, necessitating immediate compensating controls. Additionally, the presence of public exploit code raises the risk of automated attacks targeting vulnerable systems across Europe.

Mitigation Recommendations

1. Implement strict network segmentation and firewall rules to restrict access to the Tipray Data Leakage Prevention System, limiting exposure to trusted internal IPs only. 2. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'sort' parameter in findUserPage.do requests. 3. Conduct thorough input validation and sanitization on all user-supplied parameters, especially 'sort', using allowlists and parameterized queries if possible. 4. Monitor database logs and application logs for unusual query patterns or errors indicative of SQL injection attempts. 5. If feasible, isolate the vulnerable system from internet-facing networks or use VPNs to control access. 6. Engage with the vendor or community to seek patches or updated versions; if unavailable, consider alternative DLP solutions. 7. Perform regular security assessments and penetration tests focusing on web application vulnerabilities. 8. Educate security teams about this specific vulnerability and ensure incident response plans include detection and mitigation steps for SQL injection attacks. 9. Apply network intrusion detection systems (NIDS) signatures that can identify exploitation attempts. 10. Backup critical data regularly to enable recovery in case of data integrity compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-10-05T06:06:52.583Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68e3271594eb61166fa5265a

Added to database: 10/6/2025, 2:19:01 AM

Last enriched: 10/13/2025, 11:09:33 AM

Last updated: 11/22/2025, 3:18:42 PM

Views: 47

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats