CVE
Wavelog unauthenticated SQL injection in OQRS callsign log search
Affects Wavelog versions before 2.4.2 where the OQRS callsign log search endpoint is reachable. The advisory says users must upgrade to a version newer than 2.4.2.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.5.
Summary
Wavelog, a web-based amateur radio logging application, has an SQL injection flaw in its OQRS callsign log search that can be reached remotely without logging in. An attacker can read sensitive application data, including account details, password hashes, API keys, and station credentials, and can use exposed password reset tokens to take over accounts, including administrator accounts.
Original description
Wavelog is web-based amateur radio logging software. Prior to 2.5, the callsign parameter accepted by POST /oqrs/search_log in application/controllers/Oqrs.php search_log() reaches application/models/Oqrs_model.php search_log(), where it is concatenated directly into a raw SQL WHERE clause without parameter binding. An unauthenticated remote attacker can use UNION-based SQL injection to read arbitrary application database records, including account data, password hashes, API keys, station credentials, reset tokens, QSO data, and station metadata. Disclosure of password reset tokens can be combined with the forgot_password workflow to take over accounts, including administrator accounts. This issue is fixed in version 2.5.
Who should check
Operators of network-reachable Wavelog instances below 2.4.2 that run the OQRS callsign log search endpoint, including amateur radio stations and clubs hosting Wavelog.
“An unauthenticated SQL injection vulnerability exists in the OQRS callsign log search endpoint”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade 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-55508 (Wavelog has unauthenticated SQL injection in the OQRS callsign log search), 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-55508 (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 versions before 2.4.2 (the advisory's affected range), with the OQRS callsign log search endpoint reachable (source: https://github.com/wavelog/wavelog/security/advisories/GHSA-rrrq-ch2q-pqmp)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-55508 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55508 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-rrrq-ch2q-pqmp
- https://github.com/wavelog/wavelog/pull/3293
- https://github.com/wavelog/wavelog/commit/b65ecbfad21f4c14a4ae225b9f804c756701698c
- 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-55508
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-55508"}.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-rrrq-ch2q-pqmp |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-55508 |
| Record | NVD · CVE-2026-55508 |
| Other links 3 | |
| Repository | GitHub · wavelog/wavelog · Pull request #3293 |
| Repository | GitHub · wavelog/wavelog · Commit b65ecbfa |
| 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-55508
Is CVE-2026-55508 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?
SQL injection in the OQRS callsign log search lets an unauthenticated remote attacker use UNION-based queries to read arbitrary application database records. These include user accounts with bcrypt password hashes, API keys, station credentials, password reset tokens, QSO data and station metadata. Reset tokens can be used to take over accounts, including administrator accounts.Source: github.com
Which versions are affected by CVE-2026-55508?
wavelog: before 2.5.Source: cve.now feed data
Am I affected, and how do I check?
The advisory's affected range is Wavelog versions before 2.4.2, and only where the OQRS callsign log search endpoint is reachable. To check a installation, look at the installed Wavelog version and whether that endpoint can be reached without logging in.Source: github.com
How do I fix CVE-2026-55508?
The advisory says users must upgrade to a version newer than 2.4.2. The checked facts do not name a specific fixed release.Source: github.com