Munshi IDOR via Purchase Inquiry Thread Endpoint
Munshi (by Petpooja) versions before 2026-06-17 contain a broken object level authorization flaw in the purchase inquiry thread endpoint. No vendor rating or fix is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Munshi versions before 2026-06-17 are affected
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Munshi, a business software product from Petpooja, is affected by a flaw that lets logged-in users view other users' purchase inquiry conversations with suppliers and related quotation details. This exposes sensitive business information to people who should not have access to it.
Read the original description
Munshi (by Petpooja) before 2026-06-17 contained 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 modify the thread ID to read supplier communication and quotation-related content belonging to other users, resulting in unauthorized disclosure of sensitive business information outside their access scope.
What to do
Check whether your setup matches what the bug needs.
Munshi versions before 2026-06-17 are affectedWorkaround: The sources list no workaround or interim measure. No fix is documented, so the only listed step is to check with Petpooja for an update.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Petpooja Munshi
through 2026-06-17
Evidence 3
- Exploit
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119734
What does this mean?
The endpoint does not check that a logged-in user owns the thread they request. Changing the thread ID can expose supplier communication and quotation content that belongs to other users.Source: vulncheck.com
Am I affected, and how do I check?
Munshi by Petpooja versions released before 2026-06-17 are listed as affected. To check an installed copy, compare its version or build date against that cutoff.Source: vulncheck.com
What should I do about it?
The sources do not name a fixed version, so no upgrade target is listed. Check with Petpooja for an updated Munshi release.Source: vulncheck.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The sources list no workaround or interim measure. No fix is documented, so the only listed step is to check with Petpooja for an update.Source: vulncheck.com