CVE-2026-55383 InvoiceShelf: Public EmailLog token type confusion allows cross-company invoice disclosure
Attackers can access other companies' invoices and estimates by exploiting token type confusion and expired token handling in public routes.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-55383?
CVE-2026-55383 is a high-severity missing authorization vulnerability in InvoiceShelf, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-285
Which versions are affected by CVE-2026-55383?
How do I fix CVE-2026-55383?
No fix has been published for CVE-2026-55383 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-55383 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55383 exists.
Sources
Also known as GHSA-73q7-2953-8gvx.