CVE-2026-46622: SolidInvoice: API tokens stored as plaintext in the database allowing full credential compromise on database breach
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.
Metrics
- CVSS v3.1
- 8.1
- Severity
- HIGH
- Fixed in
- —
- Affected Products
- 1
HarborGuard Analysis
Synopsis
This is a plaintext credential storage vulnerability in SolidInvoice, an open-source invoicing platform. The vulnerability is reachable over the network and requires a low-privilege account, meaning any attacker who gains read access to the database (via SQL injection, a leaked backup, a misconfigured replica, or insider access) immediately obtains all API tokens for every user in plaintext with no decryption or cracking step required. Successful exploitation gives the attacker full API credentials, enabling them to read and tamper with any data exposed by the REST API. No fix version has been published yet; HarborGuard is tracking the advisory and will make a patched-image rebuild available the moment an upstream fix is released.
HarborGuard Coverage
Detection of CVE-2026-46622 is available across every HarborGuard environment: the CVE is ingested from upstream advisory feeds within minutes of publication and matched against customer images, including custom-built images that package SolidInvoice. Any image found running an affected version of SolidInvoice is flagged automatically.
AvailableHarborGuard is capable of scoring this finding at CVSS 8.1 (HIGH) and weighting it further against each environment's compliance policy, so teams with stricter data-handling requirements see it prioritized accordingly. Triage routing can send the finding to the inbox or ticketing integration configured for each customer org.
AvailableBecause no fix version has been published upstream, HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment SolidInvoice ships a corrected release. In the interim, customers with auto-remediation enabled can apply compensating controls (described below) through HarborGuard's policy layer without waiting for a full upstream patch.
Pending upstreamExploit Conditions
- Network reachabilityRequired
The attacker must reach the application over the network; the CVSS vector specifies AV:N, meaning no physical or local access is assumed.
- AuthenticationRequired
A low-privilege account is sufficient; the attacker needs any valid credential to reach attack vectors such as SQL injection entry points, but does not need administrative rights.
- Victim interactionNot required
No user action or social-engineering step is needed; the attacker operates entirely without victim participation.
- Attack complexityDetail
Attack complexity is Low (AC:L), meaning the exploit is reliable and requires no special timing, race conditions, or specific environmental configuration.
Blast Radius
- Reads all plaintext API tokens from the database for every user account registered in the application.
- Uses harvested tokens to authenticate to the SolidInvoice REST API as any user, reading invoices, client records, and financial data.
- Modifies or deletes invoices, payment records, and client data through the API using the stolen credentials.
How HarborGuard Handles This
Available on HarborGuard: because no upstream patch exists for CVE-2026-46622 as of the publication date, HarborGuard continuously re-checks the SolidInvoice advisory on every ingest cycle and will trigger a patched-image rebuild automatically once version 2.3.17 or a later fix release is published. For customers who opt into auto-remediation, that rebuild will be followed by a regression-test run and a PR opened against affected workloads with no manual intervention required. While no patch is available, recommended compensating controls include restricting database replica access to the minimum required principals, enabling egress filtering to reduce the exposure surface for SQL injection exfiltration paths, and auditing or rotating API tokens for any accounts whose database access logs show anomalous read activity. Customers can configure HarborGuard network-policy rules to isolate the SolidInvoice database tier from broader internal network segments, reducing the blast radius of a read-access breach.
- SolidInvoice / SolidInvoice< 2.3.17
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N