CVE-2026-119731
Deferred Deferred - Pending Action

Munshi Payment Bypass via Unauthenticated Webhook

Vulnerability report for CVE-2026-119731, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-02
Last Modified
2026-11-02
Generated
2026-11-02
AI Q&A
2026-11-02
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Petpooja Munshi 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
CWE-345 The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a payment bypass flaw in Munshi (by Petpooja) before 2026-06-30. The subscription payment webhook at POST /api/payment/order/webhook lacks authentication, cryptographic verification, and source validation. An attacker can forge a payment-success notification using an order ID obtained from a payment-status redirect URL, tricking the system into granting paid access without actual payment.

Detection Guidance

Detecting this vulnerability requires checking for unauthenticated webhook endpoints handling payment notifications. Inspect network traffic for POST requests to /api/payment/order/webhook without authentication headers or signature verification. Monitor logs for suspicious subscription activations without corresponding payment provider confirmations.

Impact Analysis

An attacker could exploit this to gain unauthorized paid access to services without paying. This could lead to financial losses for the service provider and potential disruption of legitimate paid services. Users might experience unauthorized access or service interruptions if the system incorrectly grants access.

Mitigation Strategies

Immediately disable the affected webhook endpoint or restrict access via IP whitelisting. Implement cryptographic signature verification for webhook payloads and require authentication tokens. Verify all subscription activations by cross-checking with the payment provider's server before granting paid access.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119731. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...