Munshi (by Petpooja) vulnerabilities

Munshi (by Petpooja) before 2026-07-13 contains a stored cross-site scripting vulnerability that allows authenticated users to inject malicious markup through item descriptions or messages in the Purchase Inquiry thread. The payload is assigned to innerHTML during rendering before text cleaning completes, enabling JavaScript execution in the browser of another user who opens the thread.

Munshi (by Petpooja) before 2026-06-17 contains a broken object level authorization vulnerability that allows authenticated attackers to access another user's purchase inquiry by manipulating the thread identifier in the GET /purchase-inquiry/thread/{thread-id} endpoint. Attackers can read supplier communication and quotation content belonging to other users.

Munshi (by Petpooja) before 2026-07-28 contains a broken object level authorization vulnerability that allows authenticated sub-users to delete invoices belonging to the tenant owner via the DELETE /api/invoice/{invoice_id} and POST /api/invoices/bulk-delete endpoints. The endpoints only verify tenant membership without enforcing object-level ownership or permission checks.

Munshi (by Petpooja) before 2026-06-30 contained a payment bypass vulnerability in its subscription payment webhook at POST /api/payment/order/webhook, which lacks webhook authentication, cryptographic signature verification, source validation, and independent server-side confirmation with the payment provider. A remote, unauthenticated attacker can submit a forged payment-success notification referencing an order obtained from the payment-status redirect URL, causing the backend to mark the subscription as paid/active and granting paid access without an actual successful payment.