Live › vulnerability › CVE-2026-119733
Munshi (Petpooja's restaurant business app) did not check the company_delete permission or company ownership on DELETE /api/companies/{company_id}. Any invited sub-user with access to a company could delete it. VulnCheck and the researcher describe the deletion as permanent, with risk to linked invoices, configurations and chat sessions. The researcher says the linked-record effects are potential, not shown for every record. The researcher's staging test showed a soft-delete marker.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 19:24 UTC. All times on this page are UTC.
Teams that use the hosted Munshi product with invited sub-users. The flaw is in the company deletion endpoint, so any account invited to a company could reach it; the sources do not say which Munshi versions or plans are hosted versus self-run. Teams not using Munshi can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Munshi | vendor | <= 2026-07-07 | 2026-07-07 |
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Munshi (by Petpooja) before 2026-07-07 contained a missing authorization vulnerability in its company deletion workflow at DELETE /api/companies/{company_id}, where the application fails to enforce the dedicated company_delete permission or verify company ownership. An authenticated invited sub-user with mere access to a company can exploit this flaw to perform a hard delete of the company record, causing irreversible loss of associated business data including invoices, configurations, and chat sessions.
This page as .md · .json · in your agent: get_signal("CVE-2026-119733")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.