CVSS 4.0
8.7 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NCVE-2026-119731
High (8.7). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
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.
Severity
CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 19th percentile. Scored 2026-11-04. A forecast for this CVE across the internet, not for your own systems.
- CWEs
- CWE-306 Missing Authentication for Critical Functionality
CWE-345 Insufficient Verification of Data Authenticity - Published
- Modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-119731 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-119731?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-119731?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-119731 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Attack patterns (CAPEC)
- CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
- CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
- CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
- CAPEC-166 Force the System to Reset Values Severity: Medium
- CAPEC-216 Communication Channel Manipulation
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).