# CVE-2026-54237: Wavelog: Unauthenticated Remote Code Execution

> Unauthenticated attackers can inject code into PHP configuration files via exposed install scripts, leading to remote code execution on Wavelog servers.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-jxjv-chgm-rh36

## What is CVE-2026-54237?

CVE-2026-54237 is a critical code injection vulnerability in wavelog, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wavelog is web-based amateur radio logging software. From 1.8 until 2.4.2, Wavelog exposes /install/ajax.php and /install/includes/interface_assets/triggers.php after installation without an installation lock or permission check. Unsanitized input reaches write_config() and write_configfile() in install/includes/core/core_class.php, allowing a remote unauthenticated attacker to read or write log files and place attacker-controlled content into PHP configuration files. The resulting PHP configuration content can execute on the server. This issue is fixed in version 2.4.2.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-54237?


## How do I fix CVE-2026-54237?

No fix has been published for CVE-2026-54237 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54237 being exploited?

There is no known exploitation of CVE-2026-54237 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54237 and fix it if it is affected.

What it is: CVE-2026-54237 is a critical code injection vulnerability in wavelog, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54237 in the wild and no public exploit code.

Affected product: wavelog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54237/ (Markdown: https://insights.sbomify.com/CVE-2026-54237/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54237
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54237
- OSV: https://osv.dev/vulnerability/CVE-2026-54237

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54237/
Summaries are generated and may contain mistakes; the official description above is the record.