# CVE-2025-11313: Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findRolePage.do findRolePage sql injection

> Remote attackers can exploit SQL injection in the findRolePage function to read or modify data, requiring immediate attention from users of this DLP system.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2025
- **Updated:** 6 Oct 2025
- **Also known as:** GHSA-pqf7-qw7f-m895

## What is CVE-2025-11313?

CVE-2025-11313 is a medium-severity SQL injection vulnerability in Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 1.0. This impacts the function findRolePage of the file findRolePage.do. This manipulation of the argument sort causes sql injection. The attack may be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-11313?

It affects 1 product.


Products: Tipray Data Leakage Prevention System.

## How do I fix CVE-2025-11313?

No fix has been published for CVE-2025-11313 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11313 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11313 exists.

## Other vulnerabilities in Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统

- [CVE-2025-11311](https://insights.sbomify.com/CVE-2025-11311/): Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findTenantPage.do findTenantPage sql injection (medium 6.9)
- [CVE-2025-11312](https://insights.sbomify.com/CVE-2025-11312/): Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findModulePage.do findModulePage sql injection (medium 6.9)
- [CVE-2025-11314](https://insights.sbomify.com/CVE-2025-11314/): Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findSingConfigPage.do findRolePage sql injection (medium 6.9)
- [CVE-2025-11315](https://insights.sbomify.com/CVE-2025-11315/): Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findUserPage.do findUserPage sql injection (medium 6.9)
- [CVE-2025-11316](https://insights.sbomify.com/CVE-2025-11316/): Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统 findCategoryPage.do findCategoryPage sql injection (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11313 and fix it if it is affected.

What it is: CVE-2025-11313 is a medium-severity SQL injection vulnerability in Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11313 exists.

Affected product: Tipray 厦门天锐科技股份有限公司 Data Leakage Prevention System 天锐数据泄露防护系统. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11313/ (Markdown: https://insights.sbomify.com/CVE-2025-11313/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11313
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11313
- OSV: https://osv.dev/vulnerability/CVE-2025-11313

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11313/
Summaries are generated and may contain mistakes; the official description above is the record.