CVE-2026-55561: InvoicePlane: Guest user IDOR in quote approval and rejection

Published Oct 28, 2026
·
Updated

InvoicePlane is a self-hosted open source application for managing invoices, clients, and payments. Prior to 1.7.2-beta-1, guest users can approve or reject quotes belonging to any client, not just their assigned clients. The approve() and reject() methods in the Guest Quotes controller, application/modules/guest/controllers/Quotes.php, call approvequotebyid($quoteid) and rejectquotebyid($quoteid) directly without the wherein('ipquotes.clientid', $this->userclients) scoping that sibling methods use. A guest user assigned to one client can change another client's quote status by supplying sequential integer quoteid values, and emailquotestatus() also sends notification emails. Additionally, generatepdf() calls markviewed($quoteid) before checking the client scope, allowing a guest user to mark another client's quote as viewed. These issues are fixed in version 1.7.2-beta-1 and the subsequent stable version 1.7.2.

Affected Software

1 affected component
InvoicePlane InvoicePlane<1.7.2-beta-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade InvoicePlane to a version that resolves this vulnerability.

    Fixed in 1.7.2

Event History

Oct 28, 2026
CVE Published
via MITRE·10:33 PM
Data Sourced
via MITRE·10:33 PM
DescriptionWeakness

Frequently Asked Questions

1

Who can exploit this issue?

A guest user who is assigned to at least one client can exploit it. They can target quotes belonging to other clients by supplying sequential integer quote_id values.

2

What actions can an attacker perform?

An affected guest user can approve or reject another client's quote, which also triggers quote-status notification emails. They can also mark another client's quote as viewed through PDF generation.

3

Are guest users limited to their assigned clients on affected versions?

Not for quote approval, rejection, or the viewed-status update described here. The affected controller methods do not apply the client-scope check used by sibling methods.

4

Which versions contain the fix?

The issue is fixed in 1.7.2-beta-1 and in the subsequent stable release, 1.7.2.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203