Skip to main content
Menu
CVEs

CVE

Wavelog local file read in LotW import feature

CVE-2026-55505Published Updated Summary written by a model

4.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.2.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.2.4.

Summary

Wavelog, a web-based amateur radio logging application, has a flaw in its LotW import feature that lets an attacker read files from the server, including environment data, mounted secrets, and application configuration. An attacker can exploit it remotely, after logging in with high privileges, and the issue is fixed in a later release.

Original description

Wavelog is web-based amateur radio logging software. Prior to 3.2.4, the application/controllers/Lotw.php import() workflow passes the lotw_download_url configuration value to curl without scheme validation, accepts file:// content, and writes the response to a predictable path under ./uploads/ that can be retrieved through an unauthenticated HTTP request. A standard user can trigger the LotW import, although changing lotw_download_url normally requires installer administrator access, and related vulnerabilities can remove that prerequisite. The same missing status-validation pattern affects the LotW lotw_users fetch helper and per-user download helper. This exposes files readable by the www-data user, including environment data, mounted secrets, and application configuration. This issue is fixed in version 3.2.4.

cve.now Index

8Pcve.now Index 8 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.9/10CVSS 4.9
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.2.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-55505 (Wavelog: Authenticated SSRF-to-Local-File-Read via LotW Import file:// Scheme), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-55505 (entry last updated 2026-11-18):
Affected:
- wavelog wavelog: fixed in 3.2.4
Fixed versions: 3.2.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-55505 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55505 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/wavelog/wavelog/security/advisories/GHSA-5xph-jv49-jjr8
- https://github.com/wavelog/wavelog/pull/3886
- https://github.com/wavelog/wavelog/commit/6f16eaccea942e2fb91af4658ce4ae106087daec
- https://github.com/wavelog/wavelog/releases/tag/3.2.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-55505
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-55505"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • wavelog wavelog

    fixed in 3.2.4

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · wavelog/wavelog · Advisory GHSA-5xph-jv49-jjr8
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-55505
RecordNVD · CVE-2026-55505
Other links 3
RepositoryGitHub · wavelog/wavelog · Pull request #3886
RepositoryGitHub · wavelog/wavelog · Commit 6f16eacc
RepositoryGitHub · wavelog/wavelog · Release 3.2.4

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-55505

Is CVE-2026-55505 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-55505?

wavelog: before 3.2.4.Source: cve.now feed data

How do I fix CVE-2026-55505?

Upgrade to a fixed version: 3.2.4.Source: cve.now feed data

More CVEs