Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-52562 is a critical-severity Path Traversal (CWE-22) vulnerability. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 24% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Convoy is a KVM server management panel for hosting providers, and versions 3.9.0-rc3 through 4.4.0 contain a directory traversal vulnerability in the LocaleController component. The flaw, tracked as CVE-2025-52562 and assigned CWE-22 and CWE-98, permits an unauthenticated remote attacker to supply crafted locale and namespace parameters in an HTTP request that results in the inclusion and execution of arbitrary PHP files on the server. The issue carries a CVSS 3.1 score of 10.0, reflecting network-accessible exploitation with no required credentials or user interaction and full confidentiality, integrity, and availability impact under a changed scope.
An attacker can send a single malicious request to the affected endpoints and achieve arbitrary code execution on the underlying server, potentially leading to full compromise of the management panel and any hosted virtual machines. Because the vulnerability is unauthenticated, exploitation can originate from any internet-reachable system without prior access or authentication.
The vulnerability was addressed in version 4.4.1, as noted in the project’s GitHub security advisory GHSA-43g3-qpwq-hfgg and the associated commit that hardened the LocaleController parameter handling. A temporary workaround recommended in the advisory is the deployment of strict Web Application Firewall rules that block or sanitize incoming requests targeting the vulnerable endpoints.
The EPSS score remains flat at 0.0378 with no material increase after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-18951
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Developer testing and static analysis can discover missing filename restrictions before deployment.
Input validation directly neutralizes special path elements before pathname construction occurs.
Information-flow rules can block the loading of external or unauthorized files into the PHP process.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.
Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.