CVE-2025-63414VulnerabilityPublished 16 Dec 2025

CVE-2025-63414: n/a

Source CVE Database V5

Not known to be exploited · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

10.0Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.8% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediately restrict network access to the /html/execute.php endpoint by implementing firewall rules or network segmentation to limit exposure to trusted IP addresses only. 2. Monitor web server logs for suspicious requests targeting the id parameter or unusual command execution patterns. 3. Deploy web application firewalls (WAFs) with custom rules to detect and block path traversal and command injection attempts targeting this endpoint. 4. Conduct thorough code reviews and input validation improvements to sanitize the id parameter and prevent directory traversal and command injection. 5. Engage with the Allsky WebUI vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available. 6. Implement intrusion detection systems (IDS) tuned to detect exploitation attempts of this specific vulnerability. 7. Educate IT and security teams about the vulnerability and ensure incident response plans include scenarios involving remote code execution attacks. 8. Consider isolating or decommissioning vulnerable instances until a secure version is deployed. 9. Regularly back up critical data and verify recovery procedures to mitigate potential damage from exploitation.

Description

CVE-2025-63414 is a critical path traversal vulnerability in the Allsky WebUI that allows unauthenticated remote attackers to execute arbitrary commands on the underlying operating system via a crafted HTTP request to the /html/execute.php endpoint. This leads to full remote code execution without requiring authentication or user interaction. The vulnerability stems from improper input validation in the id parameter, enabling attackers to traverse directories and inject OS commands. With a CVSS score of 10.0, this flaw impacts confidentiality, integrity, and availability severely. Although no known exploits are currently reported in the wild, the ease of exploitation and the critical impact make it a significant threat. European organizations using Allsky WebUI are at risk, especially those in countries with higher adoption of this software or strategic targets for cyberattacks. Immediate mitigation involves restricting access to the vulnerable endpoint, applying patches once available, and implementing network-level protections. Countries like Germany, France, and the UK are likely most affected due to their technological infrastructure and usage patterns.

Impact

For European organizations, this vulnerability poses a severe risk due to the potential for complete system compromise without any authentication barrier. Confidentiality is at risk as attackers can access sensitive data stored or processed by the affected systems. Integrity is compromised because attackers can alter system files, configurations, or data. Availability is threatened as attackers could disrupt or disable services by executing destructive commands. Critical infrastructure, research institutions, and enterprises using Allsky WebUI could face operational disruptions, data breaches, and reputational damage. The vulnerability’s exploitation could also facilitate lateral movement within networks, increasing the scope of impact. Given the high CVSS score and the lack of patches, organizations face an urgent need to assess exposure and implement mitigations. The threat is particularly acute in sectors with high-value targets or regulatory requirements for data protection, such as finance, healthcare, and government entities across Europe.

Summary

CVE-2025-63414 is a critical security vulnerability identified in the Allsky WebUI, specifically in the version dated 2024.12.06_06. The flaw is a path traversal vulnerability (CWE-22) combined with command injection (CWE-78) that allows an unauthenticated remote attacker to achieve arbitrary command execution on the server hosting the WebUI. The vulnerability exists in the /html/execute.php endpoint where the id parameter is improperly sanitized, enabling attackers to craft HTTP requests that traverse directories and inject operating system commands. This results in full remote code execution (RCE) with no authentication or user interaction required. The CVSS v3.1 score is 10.0, reflecting the highest severity due to network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and complete impact on confidentiality, integrity, and availability (C:H/I:H/A:H). Although no public exploits have been reported yet, the vulnerability’s nature and ease of exploitation make it a critical risk. The lack of available patches at the time of publication increases the urgency for defensive measures. The vulnerability could be exploited to take full control of affected systems, steal sensitive data, disrupt services, or use compromised hosts as pivot points in broader attacks.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #9OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
Architecture and Design
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Architecture and Design · Operation · Sandbox or Jail
Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
Architecture and Design · Attack Surface Reduction
For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the data locally in the session's state instead of sending it out to the client in a hidden form field.
OWASP Cheat Sheets
Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OS Command Injection Defense (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.5 (opens in a new tab)
V5.3.8 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Command Delimiters (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
Argument Injection (opens in a new tab)
OS Command Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 23 Dec 2025, 17:22 UTC

WeaknessesCWE-22, CWE-78

Technical details

References

Community reviews

Related threats