External risk intelligence

Wavelog Path Traversal Leading to Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-55506

Wavelog is a web-based application intended for amateur radio logging. While web applications are inherently network-accessible, amateur radio logging software is frequently deployed in private, home-lab, or club-local environments. Public internet exposure is possible if the user explicitly chooses to host it externally, but it is not a default or typical internet-facing service like a gateway or enterprise portal.

Path Traversal

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability in Wavelog, a web-based amateur radio logging software, could allow an authenticated user to delete arbitrary files. This could potentially lead to service disruptions or unauthorized access to the application. The primary concern is to confirm if this software is in use and exposed.

  • Malicious filenames can delete critical system files.
  • It could lead to service disruption or takeover.
  • Confirm relevance and exposure of Wavelog.

Attack Path

How an attacker could exploit the issue

An attacker with standard user access to Wavelog can manipulate file path data to delete arbitrary files on the server. This is achieved by associating a specially crafted filename containing directory traversal characters with a user's log entry, which is then processed by a file deletion function. Successfully exploiting this allows an attacker to disrupt service or potentially take over the application.

  • Authenticated user access is required.
  • A malicious filename triggers file deletion.
  • Risk of denial of service or takeover.

Live Threat

Current exploitation, exposure, and threat context

An authenticated user could exploit this vulnerability to delete arbitrary files on the server, potentially disrupting service or allowing for application takeover when the software is configured to allow it.

  • Server configuration and operational files.
  • Malicious filename in a QSO.
  • Denial of service or application takeover.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world action for this critical vulnerability likely involves application owners and potentially infrastructure or platform teams responsible for hosting the Wavelog software. The initial practical step is to identify all instances of Wavelog within your environment, determine their reachability and business criticality, and then locate the specific owners for each instance to begin planning remediation.

  • Identify Wavelog instances and owners.
  • Verify exposure and business criticality.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Wavelog and how is it used?

Wavelog is a web-based software application designed for amateur radio operators to log their radio contacts, or QSOs. It helps enthusiasts organize and manage their communication data. Because it runs as a web application, it is typically hosted on a server—whether that is a local home computer, a private club server, or occasionally a public-facing web server—to allow users to interact with their logbooks through a browser.

What does CVE-2026-55506 mean in simple terms?

This vulnerability is classified as Path Traversal (CWE-22) and External Control of File Name (CWE-73). Essentially, the software does not properly filter special characters that point to different file locations on the server. Because the application allows a user to define a filename during a specific request, it accidentally grants that user the ability to delete important system files outside of the intended folder when they perform a file deletion action.

How is this vulnerability triggered?

An attacker needs an authenticated user account to trigger the flaw. By crafting a filename that uses directory traversal sequences, the attacker associates this malicious name with their own log entry. When the attacker initiates a delete request, the server’s underlying PHP process follows the path provided and deletes the targeted file. Merely viewing a log or browsing the site does not trigger this; the specific, malicious delete action is required.

Is my Wavelog instance at risk of this attack?

According to Halo Surface Signal, risk depends on how your instance is hosted. While Wavelog is often found in private home-lab or club-local environments, it becomes an external risk if you have explicitly configured it to be accessible via the public internet. If your instance is only reachable within a private network, the potential for unauthorized access is lower, but you should still assess the impact if a malicious user were to gain access to your network.

What should I do if I am running Wavelog?

Your first step is to inventory all instances of Wavelog within your infrastructure to identify which ones are active and who owns them. Once identified, verify their reachability—whether they are internal or internet-facing—to prioritize updates. Since a fix is available in version 2.5, planning an upgrade for these instances is the primary technical response to resolve this security gap and prevent unauthorized file deletion.

References