dbcve.org
MetersphereApplication

CVE-2025-53639

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-14
Fix available
A fix is available. Upgrade to 3.6.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MeterSphere before version 3.6.5-lts contains a SQL injection vulnerability in the sortField parameter of certain API endpoints. The parameter is not properly validated or sanitized, allowing attackers to inject arbitrary SQL statements through the sorting functionality. This can lead to unauthorized data modification, deletion, or full database compromise.

MitigationUpgrade MeterSphere to version 3.6.5-lts or later to obtain the fix for this SQL injection vulnerability. Until patched, restrict access to vulnerable API endpoints via network segmentation or authentication controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MetersphereApplication
Affected:< 3.6.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MeterSphere installation
    Identify if MeterSphere is running in your environment. Check for MeterSphere services, containers, or processes. Look for the application through service discovery, container orchestration tools, or process listings.
    Affected if MeterSphere is present in your environment
  2. Determine the installed MeterSphere version
    Locate the version information for your MeterSphere installation. This may be accessible through the application's web interface (typically in an About or Settings page), container image tags, deployment manifests, or system configuration files.
    Affected if Version is below 3.6.5-lts (any version before the 3.6.5 release)
  3. Identify API endpoints using sortField parameter
    Review your MeterSphere API documentation or traffic logs to find API endpoints that accept a sortField parameter for sorting functionality. These are typically list, search, or report endpoints.
    Affected if The affected API endpoints with sortField parameter are accessible in your deployment
  4. Check API accessibility
    Determine if the vulnerable API endpoints are network-accessible. Check firewall rules, API gateway configurations, authentication settings, and whether the endpoints are exposed to untrusted networks.
    Affected if The API endpoints are reachable without proper network segmentation or authentication controls

Your environment is affected if MeterSphere version is less than 3.6.5-lts and the vulnerable API endpoints are accessible in your deployment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.6.5 or later
Fixed in 3.6.5
Interim mitigation

Upgrade MeterSphere to version 3.6.5-lts or later to obtain the fix for this SQL injection vulnerability. Until patched, restrict access to vulnerable API endpoints via network segmentation or authentication controls.

Recommended fix High confidence

3.6.5-lts

  1. 1. Back up the current MeterSphere installation and database before proceeding with any upgrade.
  2. 2. Stop the MeterSphere services to ensure a clean upgrade process.
  3. 3. Consult the official MeterSphere upgrade documentation for your deployment method (Docker, Kubernetes, or direct installation).
  4. 4. Upgrade MeterSphere to version 3.6.5-lts, following the standard upgrade procedure for your installation method.
  5. 5. Verify that the upgrade completed successfully and all services are running properly.
  6. 6. Test the sorting functionality in the affected API endpoints to confirm the SQL injection vulnerability is remediated.
Caveat The official description does not mention any breaking changes; however, always review release notes for any configuration or behavior changes before upgrading in production environments.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Metersphere Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53639 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data