SolidInvoice's long-lived API tokens accepted as URL query parameters, exposing credentials in server logs and browser history
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| SolidInvoice | SolidInvoice | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Solidinvoice | Solidinvoice |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.366% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Solidinvoice
Solidinvoice solidinvoice |
|
| Vendors & Products |
Solidinvoice
Solidinvoice solidinvoice |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | SolidInvoice's long-lived API tokens accepted as URL query parameters, exposing credentials in server logs and browser history | |
| Weaknesses | CWE-598 | |
| References |
| |
| Metrics |
cvssV3_1
|