CVE-2026-61614

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Sep 4, 2026
Patch available. Sources: github, github_release.
github_release Patch Available

Release 3.0.1

Patch available: SolidInvoice/SolidInvoice 3.0.1

https://github.com/SolidInvoice/SolidInvoice/releases/tag/3.0.1
github Patch Available

Long-lived API tokens accepted as URL query parameters, exposing credentials in server logs and browser history · Advisory · SolidInvoice/SolidInvoice · GitHub

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 21:24 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 20:43 UTCEG score recompute
  4. 2026-09-16 20:00 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 19:04 UTCEG score recompute
  8. 2026-09-13 17:32 UTCEG score recompute
  9. 2026-09-12 16:50 UTCEG score recompute
  10. 2026-09-11 16:08 UTCEG score recompute
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 09:37 UTCEPSS rescore
  13. 2026-09-10 15:19 UTCEG score recompute
  14. 2026-09-08 23:04 UTCEG score recompute
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 21:23 UTCEG score recompute
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 20:42 UTCEG score recompute
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-05 20:00 UTCEG score recompute
  21. 2026-09-04 19:18 UTCEG score recompute
  22. 2026-09-04 18:49 UTCEG score recompute
  23. 2026-09-04 18:31 UTCEG score recompute
  24. 2026-09-04 17:54 UTCEG score recompute
  25. 2026-09-04 17:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61614?
CVE-2026-61614 is a medium vulnerability published on September 4, 2026. 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…
When was CVE-2026-61614 disclosed?
CVE-2026-61614 was first published in the National Vulnerability Database on September 4, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61614 actively exploited?
CVE-2026-61614 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.9% of all scored CVEs.
What is the CVSS score of CVE-2026-61614?
CVE-2026-61614 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-61614?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61614, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61614

Explore →

Is Your Infrastructure Affected by CVE-2026-61614?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs