Quick answers
- Is CVE-2026-46622 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46622 being exploited in the wild.
- How severe is CVE-2026-46622?
- High severity, with a CVSS score of 8.1, published 11 June 2026.
- Which products and versions are affected?
- SolidInvoice <= 2.3.16.
- Is there a fix for CVE-2026-46622?
- A patch was published on 2026-05-15: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46622 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-46622?
- Check whether you run SolidInvoice at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
SolidInvoice prior to version 2.3.17 suffers from CWE-312 (Cleartext Storage of Sensitive Information). While API tokens are generated with sufficient entropy, they are stored as raw strings in the `api_tokens` database table and authenticated using simple plaintext equality checks in `ApiTokenRepository.php`. An attacker who gains read access to the database via SQL injection, misconfigured backups, or insider access can retrieve these tokens to perform unauthorized REST API requests. The vulnerability has been addressed in version 2.3.17 by migrating to HMAC-SHA256 hashing (keyed by the application secret) for token storage and verification.
Affected products
- SolidInvoice SolidInvoice <= 2.3.16
Timeline
- 2026-05-15: patched: Fix committed to repository
- 2026-05-18: advisory: GitHub Security Advisory published
- 2026-06-11: disclosed: CVE published to NVD