CVE-2025-63414
CVE-2025-63414 is a critical-severity vulnerability in Allskyteam Allsky with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.
Key facts
- Severity: Critical (CVSS 3.x base score 10.0)
- EPSS exploit prediction: 2% (81st percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-203804
- Weakness: CWE-22
- Affected product: Allskyteam Allsky
- Published:
- Last modified:
Description
A Path Traversal vulnerability in the Allsky WebUI version v2024.12.06_06 allows an unauthenticated remote attacker to achieve arbitrary command execution. By sending a crafted HTTP request to the /html/execute.php endpoint with a malicious payload in the id parameter, an attacker can execute arbitrary commands on the underlying operating system, leading to full remote code execution (RCE).
Frequently asked questions
- What is CVE-2025-63414?
- A Path Traversal vulnerability in the Allsky WebUI version v2024.12.06_06 allows an unauthenticated remote attacker to achieve arbitrary command execution. By sending a crafted HTTP request to the /html/execute.php endpoint with a malicious payload in the id parameter, an attacker can execute arbitrary commands on the underlying operating system, leading to full remote code execution (RCE).
- How severe is CVE-2025-63414?
- CVE-2025-63414 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2025-63414 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-63414?
- CVE-2025-63414 affects Allskyteam Allsky. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2025-63414?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- Does CVE-2025-63414 have an EU (EUVD) identifier?
- Yes. CVE-2025-63414 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-203804.
- When was CVE-2025-63414 published?
- CVE-2025-63414 was published on 2025-12-16 and last updated on 2026-06-17.
References
- https://gh0stmezh.wordpress.com/2025/12/02/cve-2025-63414/
- https://github.com/AllskyTeam/allsky
- https://github.com/AllskyTeam/allsky/blob/master/html/execute.php
Affected products (1)
- cpe:2.3:a:allskyteam:allsky:2024.12.06_06:*:*:*:*:*:*:*
More vulnerabilities in Allskyteam Allsky
- CVE-2025-65573 — High (CVSS 8.8): Cross Site Request Forgery (CSRF) vulnerability in AllskyTeam AllSky v2024.12.06_06 allows remote attackers to cause a…
- CVE-2025-65572 — Medium (CVSS 6.1): Cross Site Scripting (XSS) vulnerability in AllskyTeam AllSky v2024.12.06_06 allows remote attackers to execute…
All CVEs affecting Allskyteam Allsky →
Other CWE-22 (Path Traversal) vulnerabilities
- CVE-2026-77312 — Critical (CVSS 10.0): Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the earlier CVE-2026-67429…
- CVE-2026-121351 — Critical (CVSS 10.0): Adobe Connect is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')…
- CVE-2026-121489 — Critical (CVSS 10.0): Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache Juneau. The…
- CVE-2026-122013 — Critical (CVSS 10.0): A vulnerability was detected in Comfast CF-WR632AX 2.6.0.1. Affected by this vulnerability is an unknown functionality…
- CVE-2026-61738 — Critical (CVSS 10.0): SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to…
- CVE-2026-112690 — Critical (CVSS 10.0): This issue was addressed with improved input validation. This issue is fixed in iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2…