How severe is CVE-2026-61614?

CVE-2026-61614 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-61614 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-61614?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-61614 published?

CVE-2026-61614 was published on 2026-09-04 and last updated on 2026-09-10.

CVE-2026-61614

CVE-2026-61614 is a medium-severity vulnerability with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-598.

Key facts

Severity: Medium (CVSS 3.x base score 5.9)
EPSS exploit prediction: 0% (28th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-598
Published: 2026-09-04
Last modified: 2026-09-10

Description

SolidInvoice is an open-source invoicing platform. Prior to version 3.0.1, the REST API authenticator accepts bearer tokens via a `?token=` URL query parameter as a fallback to the `X-API-TOKEN` header. This causes long-lived API credentials to be recorded in server access logs, proxy logs, browser history, and HTTP Referer headers sent to third-party origins. Version 3.0.1 fixes the issue.

Frequently asked questions

What is CVE-2026-61614?: SolidInvoice is an open-source invoicing platform. Prior to version 3.0.1, the REST API authenticator accepts bearer tokens via a `?token=` URL query parameter as a fallback to the `X-API-TOKEN` header. This causes long-lived API credentials to be recorded in server access logs, proxy logs, browser history, and HTTP Referer headers sent to third-party origins. Version 3.0.1 fixes the issue.
How severe is CVE-2026-61614?: CVE-2026-61614 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-61614 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-61614?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-61614 published?: CVE-2026-61614 was published on 2026-09-04 and last updated on 2026-09-10.

References

Other CWE-598 vulnerabilities

CVE-2026-76179 — Critical (CVSS 9.8): An improper protection of authentication tokens vulnerability exists in certain Ebyte gateway products. Authentication…
CVE-2026-74880 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 accept refresh tokens as URL query parameters in keyserver and telemetry server…
CVE-2025-69270 — Critical (CVSS 9.8): Information Exposure Through Query Strings in GET Request vulnerability in Broadcom DX NetOps Spectrum on Windows,…
CVE-2023-6014 — Critical (CVSS 9.8): An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment.
CVE-2025-56551 — High (CVSS 8.2): An issue in DirectAdmin v1.680 allows unauthorized attackers to manipulate the page layout and replace the legitimate…
CVE-2021-21594 — High (CVSS 8.2): Dell PowerScale OneFS versions 8.2.2 - 9.1.0.x contain a use of get request method with sensitive query strings…

Browse all CWE-598 vulnerabilities →