dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-52562

CRITICAL · 10.0 CVSS v3.1 Published 2025-06-23
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Convoy is a KVM server management panel for hosting businesses. In versions 3.9.0-rc3 to before 4.4.1, there is a directory traversal vulnerability in the LocaleController component of Performave Convoy. An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted HTTP request with malicious locale and namespace parameters. This allows the attacker to include and execute arbitrary PHP files on the server. This issue has been patched in version 4.4.1. A temporary workaround involves implementing strict Web Application Firewall (WAF) rules to incoming requests targeting the vulnerable endpoints.

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

A critical directory traversal vulnerability in the LocaleController component of Convoy KVM server management panel allows unauthenticated remote attackers to execute arbitrary PHP files via malicious locale and namespace HTTP parameters. This is a remote code execution (RCE) vulnerability affecting versions 3.9.0-rc3 through 4.4.0.

MitigationUpgrade to version 4.4.1 or later. As a temporary measure, implement strict WAF rules to block directory traversal attempts on the vulnerable endpoints.

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

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Convoy KVM panel installation
    Identify if the Convoy KVM server management panel is running in your environment by checking for its web interface on typical ports (80/443) or searching for its characteristic files/directories on the web server.
    Affected if The Convoy KVM management panel is present and accessible on the network.
  2. Check installed version against fixed release
    Locate the version information for your Convoy KVM installation (typically found in admin interface, about page, or version file) and compare it to version 4.4.1.
    Affected if The installed version is lower than 4.4.1.
  3. Verify LocaleController component exists
    Check for the presence of the LocaleController component in the web application structure, typically at a path like /locale or /index.php/Locale or similar endpoint handling locale operations.
    Affected if The LocaleController component is present and accessible.
  4. Test parameter accessibility without authentication
    Send an HTTP request to the locale endpoint with directory traversal patterns in locale and namespace parameters (e.g., ../../etc/passwd) without providing credentials to verify if the vulnerability is exploitable.
    Affected if The application accepts and processes directory traversal sequences in locale or namespace parameters without authentication.

If Convoy KVM panel is present and the version is below 4.4.1 with the LocaleController accessible without authentication, the environment is affected by this vulnerability.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to version 4.4.1 or later. As a temporary measure, implement strict WAF rules to block directory traversal attempts on the vulnerable endpoints.

Recommended fix High confidence

4.4.1

  1. Backup the Convoy installation directory and database before proceeding with the upgrade
  2. Download Convoy version 4.4.1 from the official Performave repository or source
  3. Replace the existing Convoy files with the new version 4.4.1 files, preserving configuration files where applicable
  4. Run any provided database migration scripts included in the 4.4.1 release
  5. Restart the Convoy web service and PHP-FPM if applicable
  6. Verify the upgrade was successful by checking the Convoy admin panel version information
  7. Test the LocaleController functionality to confirm the path traversal vulnerability is patched
  8. Implement WAF rules as an additional layered security measure for requests targeting locale and namespace parameters
Caveat Review release notes for 4.4.1; as a major panel upgrade, test in staging environment first

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52562 — 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-52562 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