CVE-2025-11316

7.3

Tipray · Data Leakage Prevention System

Tipray Data Leakage Prevention System 1.0 is vulnerable to unauthenticated SQL injection via the tenantId parameter in the findCategoryPage.do function, allowing remote database manipulation.

Executive summary

An unauthenticated SQL injection vulnerability in Tipray Data Leakage Prevention System 1.0 allows remote attackers to execute arbitrary database queries, posing a severe risk to data confidentiality and integrity.

Vulnerability

The application is susceptible to SQL injection through the tenantId parameter within the findCategoryPage.do endpoint. An unauthenticated remote attacker can inject malicious SQL commands that are directly concatenated into database queries at the mapper layer.

Business impact

Successful exploitation permits an attacker to interact directly with the backend database, potentially leading to unauthorized data exfiltration, modification, or total compromise of the application data store. While the CVSS score of 7.3 reflects a high severity, the ability for an unauthenticated attacker to execute arbitrary code against the database layer represents a significant threat to organizational security and compliance.

Remediation

Immediate Action: As no vendor patch is currently available, restrict network access to the affected interface and implement strict input validation for all parameters passed to the findCategoryPage.do endpoint.

Proactive Monitoring: Review web server and database logs for anomalous query patterns, specifically looking for SQL syntax errors or unexpected time-based delays consistent with exploitation attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection patterns targeting the identified vulnerable parameter.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists as detailed in the technical write-up referenced by the CVE record.

Analyst recommendation

Given the public availability of exploit code and the unauthenticated nature of this vulnerability, organizations should prioritize isolating the affected system from public-facing networks. Until the vendor provides a security update, constant monitoring and the implementation of robust WAF rules remain the primary defenses against potential compromise.

Sources

Originally found and disclosed by nu11 (VulDB User), per the CVE Program record.