# CVE-2026-119731: Petpooja Munshi payment bypass in webhook

Source: https://junglewise.ai/threats/cve-2026-119731-munshi-by-petpooja-before-2026-06-30-contained-a-payment-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-02. Updated: 2026-11-02  
License: CC BY 4.0 with a link back

CVE-2026-119731 · Severity: high · CVSS 7.5 · Published 2026-11-02

Munshi, a subscription billing component by Petpooja, fails to authenticate payment confirmation webhooks, allowing attackers to forge successful payment notifications without actually paying. An unauthenticated attacker can craft a fake payment-success message to activate a subscription for free, bypassing payment collection entirely and granting access to paid services without revenue.

Technologies: [Petpooja Munshi](https://junglewise.ai/threats/technologies/munshi). Vendors: [Petpooja](https://junglewise.ai/threats/vendors/petpooja).

## Quick answers

**Is CVE-2026-119731 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119731 being exploited in the wild.

**How severe is CVE-2026-119731?** High severity, with a CVSS score of 7.5, published 2 November 2026.

**Which products and versions are affected?** Petpooja Munshi before 2026-06-30.

**Is there a fix for CVE-2026-119731?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-119731 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-119731?** Check whether you run Petpooja Munshi at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The POST /api/payment/order/webhook endpoint lacks webhook authentication, cryptographic signature verification, source validation, and independent server-side confirmation with the payment provider. An unauthenticated remote attacker can submit a forged payment-success notification referencing an order ID, causing the backend to mark the subscription as paid and active. The vulnerability requires only network access and knowledge of a valid order ID, which can be obtained from payment-status redirect URLs.

## Affected products

- Petpooja Munshi before 2026-06-30

## Timeline

- 2026-11-02: disclosed

## References

- [https://medium.com/@TheWildEye/payment-bypass-in-munshi-forging-a-phonepe-webhook-to-activate-an-unpaid-subscription-ce0806829fa4](https://medium.com/@TheWildEye/payment-bypass-in-munshi-forging-a-phonepe-webhook-to-activate-an-unpaid-subscription-ce0806829fa4)
- [https://www.petpooja.com/](https://www.petpooja.com/)

## Related threats

- [Munshi stored cross-site scripting in purchase inquiry thread](https://junglewise.ai/threats/cve-2026-119735-munshi-by-petpooja-before-2026-07-13-contained-a-stored-cross)
- [Petpooja Munshi broken object level authorization](https://junglewise.ai/threats/cve-2026-119734-munshi-by-petpooja-before-2026-06-17-contained-a-broken-object)
- [Munshi authorization bypass in company deletion](https://junglewise.ai/threats/cve-2026-119733-munshi-by-petpooja-before-2026-07-07-contained-a-missing)
- [Petpooja Munshi broken object level authorization in invoice endpoints](https://junglewise.ai/threats/cve-2026-119732-munshi-by-petpooja-before-2026-07-28-contained-a-broken-object)