# CVE-2025-53639: Metersphere has SQL Injection Vulnerability in Sorting Field

> Attackers can inject SQL via the sortField parameter to modify or delete database contents, compromising data integrity and availability.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2025
- **Updated:** 15 Jul 2025
- **Also known as:** GHSA-vcm3-5w3f-9f45

## What is CVE-2025-53639?

CVE-2025-53639 is a medium-severity SQL injection vulnerability in metersphere, published on 14 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MeterSphere is an open source continuous testing platform. Prior to version 3.6.5-lts, the sortField parameter in certain API endpoints is not properly validated or sanitized. An attacker can supply crafted input to inject and execute arbitrary SQL statements through the sorting functionality. This could result in modification or deletion of database contents, with a potential full compromise of the application’s database integrity and availability. Version 3.6.5-lts fixes the issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Metersphere Metersphere.

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

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

## Is CVE-2025-53639 being exploited?

There is no known exploitation of CVE-2025-53639 in the wild and no public exploit code.

## Other vulnerabilities in metersphere

- [CVE-2023-29944](https://insights.sbomify.com/CVE-2023-29944/): Command injection in n/a (critical 9.8)
- [CVE-2021-45790](https://insights.sbomify.com/CVE-2021-45790/): File upload in n/a (critical 9.8)
- [CVE-2021-45788](https://insights.sbomify.com/CVE-2021-45788/): SQL injection in n/a (high 8.8)
- [CVE-2023-25573](https://insights.sbomify.com/CVE-2023-25573/): Improper access control to download file in metersphere (high 8.6)
- [CVE-2022-23512](https://insights.sbomify.com/CVE-2022-23512/): Metersphere is vulnerable to Path Injection. (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53639 is a medium-severity SQL injection vulnerability in metersphere, published on 14 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53639 in the wild and no public exploit code.

Affected product: metersphere. 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-53639/ (Markdown: https://insights.sbomify.com/CVE-2025-53639/index.md)
```

## Sources

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

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