Data Leakage Prevention System
Monthly
Unrestricted file upload in Tipray Data Leakage Prevention System 1.0 allows unauthenticated remote attackers to upload arbitrary files via the uploadWxFile.do endpoint. A publicly available exploit exists, but the EPSS score of 0.06% and low CVSS impact ratings suggest limited real-world exploitation probability. No vendor patch is available.
SQL injection in Tipray Data Leakage Prevention System 1.0 allows remote attackers to manipulate the sort parameter of the findSingConfigPage.do endpoint, potentially leading to unauthorized database access. Public exploit code is available but no active exploitation has been confirmed (not in CISA KEV), and the EPSS score is a low 0.03%, indicating limited immediate risk. The vendor has not responded to disclosure and no patch is available.
SQL injection in Tipray Data Leakage Prevention System 1.0 exposes backend database contents to remote attackers via the tenantId parameter in the findCategoryPage.do endpoint, with no authentication barrier evident from the CVSS 4.0 vector. A publicly available exploit has been disclosed on GitHub, and the vendor (Xiamen Tianrui Technology, 厦门天锐科技股份有限公司) has neither responded to disclosure contact nor released a patch. Because this is a DLP product whose core function is storing sensitive file content, policy configurations, and audit logs, successful exploitation can yield high-value data theft against any confirmed deployment.
Unauthenticated SQL injection in Tipray Data Leakage Prevention System 1.0 allows remote attackers to manipulate database queries by injecting arbitrary SQL through the `sort` parameter of the `findUserPage.do` endpoint. The vendor (Tipray, a Chinese DLP appliance maker) was notified but did not respond, and a public proof-of-concept exploit has been published on GitHub. No patch is available, and EPSS exploitation probability is low (0.03%), suggesting limited widespread automated targeting despite POC availability.
SQL injection in Tipray DLP version 1.0 allows remote attackers to manipulate database queries through the 'sort' parameter in the findSingConfigPage.do endpoint. The vulnerability has a publicly available exploit, but EPSS indicates very low exploitation probability and no active exploitation confirmed by CISA KEV. Successful exploitation may lead to low-impact loss of confidentiality, integrity, or availability.
SQL injection in Tipray Data Leakage Prevention System 1.0 allows remote attackers to manipulate the sort parameter in findRolePage.do, potentially leading to unauthorized database read or modification. Public exploit code is available, but no actively exploited incidents are reported and the exploitation probability (EPSS 0.03%) is very low. The vendor has not responded to the disclosure and no patch is confirmed.
SQL injection in Tipray Data Leakage Prevention System allows remote unauthenticated attackers to inject malicious SQL via the sort parameter in findModulePage.do, compromising database confidentiality and integrity. Exploit code is publicly available, but the EPSS probability is very low (0.03%), indicating limited exploitation likelihood due to the product's niche footprint.
We are tasked with generating a comprehensive JSON analysis for CVE-2025-11311. I need to synthesize the provided data: CVE description, CVSS 4.0 vector, CWE-74, EPSS (0.03%, low), POC/exploit publicly available (from tags), CPE for Tipray Data Leakage Prevention System 1.0, references, and no KEV mentioned. I must produce JSON with specified fields. First, I'll extract key info: - Product: Tipray Data Leakage Prevention System (DLP) version 1.0, by 厦门天锐科技股份有限公司. - Vulnerability: SQL injection in function findTenantPage of file findTenantPage.do, argument sort leads to SQLi. Remote attack possible. - CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') - though typically SQLi is CWE-89, but it's labeled CWE-74, which is broader injection. I'll mention root cause as SQL injection, but CWE-74 might be a misclassification. I can note that it's an injection vulnerability leading to SQL command execution. - CVSS 4.0 vector: AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P. So network attack, low complexity, no privileges, no user interaction, vulnerable component likely the database with low impacts on confidentiality, integrity, availability. No subsequent impact. Exploit code maturity: Proof-of-concept (E:P). So it's an unauthenticated SQLi with low impact. - EPSS: 0.03% (very low exploitation probability), 9th percentile. So unlikely to be widely exploited, but POC exists. - No KEV: Not in CISA Known Exploited Vulnerabilities catalog. So no evidence of active exploitation. - Exploit availability: "The exploit has been disclosed publicly and may be used." So POC public. "Tags: SQLi, Data Leakage Prevention System" confirms. - CPE: cpe:2.3:a:tipray:data_leakage_prevention_system:1.0 indicates the specific product version. - References: includes a GitHub link to a vuln report, vuldb.com entries. The vendor did not respond. Now, I'll craft each field. product_name: "Data Leakage Prevention System" (3 word
SQL injection in Tipray Data Leakage Prevention System 1.0 allows remote unauthenticated attackers to extract or manipulate database content via the findFileServerPage.do endpoint. A publicly available exploit exists, but no vendor patch is available. EPSS score is low (0.03%), indicating limited current exploitation activity, though public availability may increase risk.
SQL injection in Tipray Data Leakage Prevention System 1.0 via the sort parameter in findDeptPage.do allows remote unauthenticated attackers to execute arbitrary SQL commands. A public exploit is available, and the vendor has not responded to the disclosure. EPSS score is low (0.03%) suggesting limited exploitation interest despite ease of exploitation.
Unrestricted file upload in Tipray Data Leakage Prevention System 1.0 allows unauthenticated remote attackers to upload arbitrary files via the uploadWxFile.do endpoint. A publicly available exploit exists, but the EPSS score of 0.06% and low CVSS impact ratings suggest limited real-world exploitation probability. No vendor patch is available.
SQL injection in Tipray Data Leakage Prevention System 1.0 allows remote attackers to manipulate the sort parameter of the findSingConfigPage.do endpoint, potentially leading to unauthorized database access. Public exploit code is available but no active exploitation has been confirmed (not in CISA KEV), and the EPSS score is a low 0.03%, indicating limited immediate risk. The vendor has not responded to disclosure and no patch is available.
SQL injection in Tipray Data Leakage Prevention System 1.0 exposes backend database contents to remote attackers via the tenantId parameter in the findCategoryPage.do endpoint, with no authentication barrier evident from the CVSS 4.0 vector. A publicly available exploit has been disclosed on GitHub, and the vendor (Xiamen Tianrui Technology, 厦门天锐科技股份有限公司) has neither responded to disclosure contact nor released a patch. Because this is a DLP product whose core function is storing sensitive file content, policy configurations, and audit logs, successful exploitation can yield high-value data theft against any confirmed deployment.
Unauthenticated SQL injection in Tipray Data Leakage Prevention System 1.0 allows remote attackers to manipulate database queries by injecting arbitrary SQL through the `sort` parameter of the `findUserPage.do` endpoint. The vendor (Tipray, a Chinese DLP appliance maker) was notified but did not respond, and a public proof-of-concept exploit has been published on GitHub. No patch is available, and EPSS exploitation probability is low (0.03%), suggesting limited widespread automated targeting despite POC availability.
SQL injection in Tipray DLP version 1.0 allows remote attackers to manipulate database queries through the 'sort' parameter in the findSingConfigPage.do endpoint. The vulnerability has a publicly available exploit, but EPSS indicates very low exploitation probability and no active exploitation confirmed by CISA KEV. Successful exploitation may lead to low-impact loss of confidentiality, integrity, or availability.
SQL injection in Tipray Data Leakage Prevention System 1.0 allows remote attackers to manipulate the sort parameter in findRolePage.do, potentially leading to unauthorized database read or modification. Public exploit code is available, but no actively exploited incidents are reported and the exploitation probability (EPSS 0.03%) is very low. The vendor has not responded to the disclosure and no patch is confirmed.
SQL injection in Tipray Data Leakage Prevention System allows remote unauthenticated attackers to inject malicious SQL via the sort parameter in findModulePage.do, compromising database confidentiality and integrity. Exploit code is publicly available, but the EPSS probability is very low (0.03%), indicating limited exploitation likelihood due to the product's niche footprint.
We are tasked with generating a comprehensive JSON analysis for CVE-2025-11311. I need to synthesize the provided data: CVE description, CVSS 4.0 vector, CWE-74, EPSS (0.03%, low), POC/exploit publicly available (from tags), CPE for Tipray Data Leakage Prevention System 1.0, references, and no KEV mentioned. I must produce JSON with specified fields. First, I'll extract key info: - Product: Tipray Data Leakage Prevention System (DLP) version 1.0, by 厦门天锐科技股份有限公司. - Vulnerability: SQL injection in function findTenantPage of file findTenantPage.do, argument sort leads to SQLi. Remote attack possible. - CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') - though typically SQLi is CWE-89, but it's labeled CWE-74, which is broader injection. I'll mention root cause as SQL injection, but CWE-74 might be a misclassification. I can note that it's an injection vulnerability leading to SQL command execution. - CVSS 4.0 vector: AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P. So network attack, low complexity, no privileges, no user interaction, vulnerable component likely the database with low impacts on confidentiality, integrity, availability. No subsequent impact. Exploit code maturity: Proof-of-concept (E:P). So it's an unauthenticated SQLi with low impact. - EPSS: 0.03% (very low exploitation probability), 9th percentile. So unlikely to be widely exploited, but POC exists. - No KEV: Not in CISA Known Exploited Vulnerabilities catalog. So no evidence of active exploitation. - Exploit availability: "The exploit has been disclosed publicly and may be used." So POC public. "Tags: SQLi, Data Leakage Prevention System" confirms. - CPE: cpe:2.3:a:tipray:data_leakage_prevention_system:1.0 indicates the specific product version. - References: includes a GitHub link to a vuln report, vuldb.com entries. The vendor did not respond. Now, I'll craft each field. product_name: "Data Leakage Prevention System" (3 word
SQL injection in Tipray Data Leakage Prevention System 1.0 allows remote unauthenticated attackers to extract or manipulate database content via the findFileServerPage.do endpoint. A publicly available exploit exists, but no vendor patch is available. EPSS score is low (0.03%), indicating limited current exploitation activity, though public availability may increase risk.
SQL injection in Tipray Data Leakage Prevention System 1.0 via the sort parameter in findDeptPage.do allows remote unauthenticated attackers to execute arbitrary SQL commands. A public exploit is available, and the vendor has not responded to the disclosure. EPSS score is low (0.03%) suggesting limited exploitation interest despite ease of exploitation.