SolidInvoice: API tokens stored as plaintext in the database allowing full credential compromise on database breach
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.197% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Solidinvoice
Solidinvoice solidinvoice |
|
| Vendors & Products |
Solidinvoice
Solidinvoice solidinvoice |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | SolidInvoice is an open-source invoicing platform. Prior to version 2.3.17, API tokens used to authenticate all REST API requests are stored as plaintext strings in the api_tokens database table. Any attacker who obtains read access to the database — through SQL injection, a leaked backup, a misconfigured replica, or insider access — immediately obtains all API credentials for every user with no further effort. This issue has been patched in version 2.3.17. | |
| Title | SolidInvoice: API tokens stored as plaintext in the database allowing full credential compromise on database breach | |
| Weaknesses | CWE-312 | |
| References |
| |
| Metrics |
cvssV3_1
|