InvoiceShelf: Public EmailLog token type confusion allows cross-company invoice disclosure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| InvoiceShelf | InvoiceShelf | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Invoiceshelf | Invoiceshelf |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.423% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Invoiceshelf
Invoiceshelf invoiceshelf |
|
| Vendors & Products |
Invoiceshelf
Invoiceshelf invoiceshelf |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| 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
|