wavelog · wavelog · CWE-22 · CWE-73 · published 2026-11-18
CVE-2026-55506Wavelog: Authenticated Arbitrary File Deletion via QSL Image Filename Path Traversal
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-55506 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 32% of all CVEs. This wavelog vulnerability: CVSS 9.6 (v3.1). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (32th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.6 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Weakness: CWE-22: Improper Limitation of a Pathname to a Restricted Directory · CWE-73: External Control of File Name or Path
Affected versions (from the CVE record)#
- wavelog wavelog
< 2.5(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.