CVE-2026-55506: Wavelog: Authenticated Arbitrary File Deletion via QSL Image Filename Path Traversal
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/Qslmodel.php deleteQsl(), which passes the planted qslimages 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Wavelogto a version that resolves this vulnerability.Fixed in 2.5
Event History
Frequently Asked Questions
Who can exploit this issue?
A standard authenticated Wavelog user can exploit it. The attacker only needs to work with their own QSO and satisfy the existing ownership check; no administrator privileges or user interaction are required.
What systems and files are at risk?
Versions before 2.5 are affected. The attacker can delete files outside their per-user QSL image directory if those files are writable by the PHP worker, including configuration or operational files that could cause denial of service.
Can this lead to more than file deletion?
Yes. If an attacker deletes installer gate files, the unauthenticated installer can become available again, allowing application identity takeover through attacker-controlled database configuration.
What should be done if upgrading cannot happen immediately?
The provided data identifies version 2.5 as the fix but does not specify a supported workaround. Prioritize upgrading and review PHP worker write permissions, since the impact is limited to files writable by that worker.