CVE-2026-46622: high-severity vulnerability in SolidInvoice
SolidInvoice: API tokens stored as plaintext in the database allowing full credential compromise on database breach
Published · Updated
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.1epss 0.3%
exploitation probability
0.3%top 83% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Affected products
SolidInvoice · SolidInvoiceRelated CVEs — SolidInvoice
In the same product, most dangerous first.
CVE-2026-61686HIGHSolidInvoice: PHP unserialize() called on client-controlled data in DataGrid LiveComponent context propEPSS 0.4%CVE-2026-46489HIGHSolidInvoice: Unrestricted file upload with no MIME validation allows stored XSS via malicious SVG logoEPSS 0.4%CVE-2026-61614MEDIUMSolidInvoice's long-lived API tokens accepted as URL query parameters, exposing credentials in server logs and browser historyEPSS 0.4%CVE-2026-61688MEDIUMSolidInvoice allows cross-user access to API token request history via writable DataGrid LiveComponent propsEPSS 0.4%CVE-2026-61608MEDIUMSolidInvoice's user invitation tokens have no expiry, allowing indefinite unauthorized company access via leaked or old invitation linksEPSS 0.3%