CVE
Wavelog arbitrary file deletion via QSL image path traversal
Affects Wavelog before 2.4.2 and Docker setups where the www-data group can write to application directories. No fixed version is confirmed yet; the advisory says to upgrade to a version newer than 2.4.2 once released.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Wavelog before 2.4.2 (the advisory's affected range) Docker setups where the www-data group has write access to install/, config and other application directories
Summary
Wavelog, a web-based amateur radio logging application, is affected. An attacker with a standard user account can reach the bug over the network by abusing the QSL image filename handling to delete arbitrary files that the PHP process can write, which can cause denial of service or, if installer gate files are removed, let the attacker reopen the installer and take over the application.
Original description
Wavelog is web-based amateur radio logging software. Prior to 2.5, the filename parameter accepted by POST /qsl/addQsoToQsl in application/controllers/Qsl.php addQsoToQsl() is stored without rejecting directory separators or relative path components, and POST /qsl/delete reaches application/models/Qsl_model.php deleteQsl(), which passes the planted qsl_images filename to unlink(). A standard authenticated user can associate the malicious filename with the user's own QSO, satisfy the ownership check, escape the per-user QSL image directory, and delete files writable by the PHP worker. Deleting configuration or operational files can cause denial of service, while deleting installer gate files can reopen the unauthenticated installer and enable application identity takeover through attacker-controlled database configuration. This issue is fixed in version 2.5.
Who should check
Teams running Wavelog before 2.4.2, including Docker deployments and any site with user accounts that can log QSOs and upload QSL images.
Not fixed by: Removing write permissions on install/ leaves the deletion primitive reachable.
“Users should upgrade to a version newer than 2.4.2 once released.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.6/10CVSS 9.6
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Wavelog before 2.4.2 (the advisory's affected range) Docker setups where the www-data group has write access to install/, config and other application directoriesUpgrade to a fixed version: 2.5.
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-55506 (Wavelog: Authenticated Arbitrary File Deletion via QSL Image Filename Path Traversal), 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-55506 (entry last updated 2026-11-18):
Affected:
- wavelog wavelog: fixed in 2.5
Fixed versions: 2.5.
Conditions (all must be true for the bug to be hit):
- Wavelog before 2.4.2 (the advisory's affected range) (source: https://github.com/wavelog/wavelog/security/advisories/GHSA-gxjg-q5fc-94q3)
- Docker setups where the www-data group has write access to install/, config and other application directories (source: https://github.com/wavelog/wavelog/security/advisories/GHSA-gxjg-q5fc-94q3)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-55506 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55506 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-gxjg-q5fc-94q3
- https://github.com/wavelog/wavelog/pull/3250
- https://github.com/wavelog/wavelog/commit/73023a2cdda5ef9b0c2f1b8a09bbd5a5fc2f1a80
- https://github.com/wavelog/wavelog/releases/tag/2.5
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-55506
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-55506"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- wavelog wavelog
fixed in 2.5
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · wavelog/wavelog · Advisory GHSA-gxjg-q5fc-94q3 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-55506 |
| Record | NVD · CVE-2026-55506 |
| Other links 3 | |
| Repository | GitHub · wavelog/wavelog · Pull request #3250 |
| Repository | GitHub · wavelog/wavelog · Commit 73023a2c |
| Repository | GitHub · wavelog/wavelog · Release 2.5 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-55506
Is CVE-2026-55506 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
What does this mean?
A filename path traversal in the QSL image handling lets an authenticated user delete arbitrary files that the PHP worker process can reach. The advisory says this can cause denial of service or, by deleting installer gate files, a takeover of the application identity layer.Source: github.com
Which versions are affected by CVE-2026-55506?
wavelog: before 2.5.Source: cve.now feed data
Am I affected, and how do I check?
The advisory's affected range is Wavelog before 2.4.2. Docker setups are also in scope where the www-data group has write access to install/, config and other application directories, which the shipped Docker container grants. To check, look at the installed Wavelog version and whether the www-data group can write to those directories.Source: github.com
How do I fix CVE-2026-55506?
The advisory says users should upgrade to a version newer than 2.4.2 once one is released. No specific fixed version is confirmed in the available facts.Source: github.com
Why do the sources disagree?
The description refers to an unauthenticated vector, but the CVSS vector lists PR:L, which means low privileges are required. The sources do not settle which one applies.Source: github.com