CVE-2026-55383
InvoiceShelf is an open-source web & mobile app that helps track …
InvoiceShelf is an open-source web & mobile app that helps track expenses, payments and create professional invoices and estimates. Prior to version 2.4.0, InvoiceShelf public customer invoice, estimate, and payment routes use an EmailLog token's numeric mailable_id without verifying mailable_type, and the JSON handlers do not enforce EmailLog::isExpired. A token issued for one document type can therefore disclose a different company's document when numeric identifiers collide, and an expired token can remain usable on the JSON routes GET /customer/invoices/{email_log:token}, GET /customer/estimates/{email_log:token}, and GET /customer/payments/{email_log:token}. View handlers can also mark a mismatched invoice or estimate as viewed and send a notification. This issue is fixed in version 2.4.0.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/InvoiceShelf/InvoiceShelf/commit/5839d8385debf379644f55e773639e1c7e673163
- github.com/InvoiceShelf/InvoiceShelf/pull/662
- github.com/InvoiceShelf/InvoiceShelf/releases/tag/2.4.0
- github.com/InvoiceShelf/InvoiceShelf/security/advisories/GHSA-73q7-2953-8gvx
- nvd.nist.gov/vuln/detail/CVE-2026-55383
- cve.org/CVERecord?id=CVE-2026-55383
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.