# CVE-2026-119731: Munshi Payment Bypass via Unauthenticated Webhook Endpoint


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-hcw8-82qq-9mcv

## What is CVE-2026-119731?

CVE-2026-119731 is a high-severity vulnerability in Petpooja Munshi, published on 2 Nov 2026. 

### Official description

Munshi (by Petpooja) before 2026-06-30 contained a payment bypass vulnerability in its subscription payment webhook at POST /api/payment/order/webhook, which lacks webhook authentication, cryptographic signature verification, source validation, and independent server-side confirmation with the payment provider. A remote, unauthenticated attacker can submit a forged payment-success notification referencing an order obtained from the payment-status redirect URL, causing the backend to mark the subscription as paid/active and granting paid access without an actual successful payment.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-119731?


## How do I fix CVE-2026-119731?

No fix has been published for CVE-2026-119731 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119731 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119731 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119731 and fix it if it is affected.

What it is: CVE-2026-119731 is a high-severity vulnerability in Petpooja Munshi, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119731 exists.

Affected product: Petpooja Munshi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119731/ (Markdown: https://insights.sbomify.com/CVE-2026-119731/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119731
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119731
- OSV: https://osv.dev/vulnerability/CVE-2026-119731

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119731/
Summaries are generated and may contain mistakes; the official description above is the record.