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