Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-54237 – Unauthenticated Remote Code Execution – Wavelog 1.8 through 2.4.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-54237 is a critical unauthenticated remote code execution vulnerability in Wavelog, a web-based amateur radio logging application. Installer endpoints remain reachable after installation completes, and unsanitized input flowing into configuration-writing functions lets a remote, unauthenticated attacker inject PHP code into configuration files that the server subsequently executes. The issue affects Wavelog versions 1.8 through 2.4.1 and is rated CRITICAL with a CVSS v4.0 base score of 9.3.

Technical details

  • Root cause: The installation endpoints /install/ajax.php and /install/includes/interface_assets/triggers.php remain accessible after Wavelog has already been installed, with no installation lock or authorization check preventing post-install access.
  • Trigger conditions: An attacker sends requests to these exposed install endpoints on a running Wavelog instance; unsanitized input from these requests reaches the write_config() and write_configfile() functions in install/includes/core/core_class.php.
  • Attack vector: Network-based, requiring no authentication and no user interaction (CWE-862: Missing Authorization).
  • Impact: Attacker-controlled content can be written into PHP configuration files, which the web server then executes, resulting in arbitrary remote code execution (CWE-94: Improper Control of Generation of Code). The vulnerability also allows reading or writing of log files, with high impact to confidentiality, integrity, and availability.

Affected software

  • Wavelog >= 1.8 and < 2.4.2

Severity

  • CVSS v4.0 Base Score: 9.3 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Wavelog to version 2.4.2 or later, which fixes this issue.
  • If patching is not immediately possible: Restrict or remove network access to the /install/ directory (including install/ajax.php and install/includes/interface_assets/triggers.php) at the web server or reverse proxy level so it cannot be reached post-installation, and ensure the installation directory is deleted or locked down after setup as recommended by the vendor.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge