InvoiceShelf bulk deletion lacks company scoping
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 v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.433% 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. In version 2.3.3 and earlier, InvoiceShelf bulk-delete request validation accepts record identifiers without consistently binding them to the authenticated user's company_id. The affected DeleteCustomersRequest, DeleteEstimatesRequest, DeleteExpensesRequest, DeleteInvoiceRequest, DeleteItemsRequest, DeletePaymentsRequest, and DeleteUserRequest validators check that identifiers exist but do not consistently check tenant ownership. An authenticated user can submit another company's identifier and delete cross-company records. This vulnerability is fixed in 2.4.0. | |
| Title | InvoiceShelf bulk deletion lacks company scoping | |
| Weaknesses | CWE-284 CWE-639 |
|
| References |
| |
| Metrics |
cvssV4_0
|