Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Sat, 17 Oct 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Invoiceshelf
Invoiceshelf invoiceshelf |
|
| Vendors & Products |
Invoiceshelf
Invoiceshelf invoiceshelf |
Wed, 14 Oct 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 14 Oct 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | InvoiceShelf: Public EmailLog token type confusion allows cross-company invoice disclosure | |
| Weaknesses | CWE-285 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-14T19:43:41.543Z
Reserved: 2026-06-16T18:57:40.182Z
Link: CVE-2026-55383
Updated: 2026-10-14T19:43:38.536Z
Status : Deferred
Published: 2026-10-14T20:17:48.350
Modified: 2026-10-15T21:08:49.703
Link: CVE-2026-55383
No data.
OpenCVE Enrichment
Updated: 2026-10-17T17:15:11Z