CVE-2026-76100
Received Received - Intake

Alipay Webhook Signature Bypass in OwnPay

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

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: GitHub, Inc.

Description

OwnPay is a self-hosted open-source payment gateway automation platform. In 0.2.0 and earlier, modules/gateways/alipay/AlipayGateway.php fails open when an Alipay callback lacks a signature or the merchant has no configured public key because verify(array $callbackData, array $credentials) falls back to an undefined mode credential that defaults to test mode, while verifyWebhook() returns true unconditionally. An unauthenticated request to POST /webhook/{gateway} can provide a pending order reference and matching amount, pass both verification gates without a valid payment signature, and cause the order and corresponding payment-received ledger entries to be marked completed. No fixed version is available as of this review.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

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

Affected Vendors & Products

Showing 5 associated CPEs
Vendor Product Version / Range
ownpay ownpay to 0.2.0 (exc)
ownpay ownpay to 0.2.1 (exc)
ownpay alipay_gateway to 1.0.1 (exc)
ownpay alipay_gateway 1.0.1
ownpay ownpay *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-347 The product does not verify, or incorrectly verifies, the cryptographic signature for data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

OwnPay is a self-hosted payment gateway platform. This vulnerability allows unsigned Alipay payment callbacks to be processed as valid due to a fallback mechanism in the verification process. The verify() function defaults to test mode when no signature or public key is configured, while verifyWebhook() accepts all requests unconditionally. This lets attackers mark orders and payments as completed without valid transactions.

Detection Guidance

Check OwnPay logs for POST /webhook/{gateway} requests with missing or invalid signatures. Look for orders marked completed without corresponding payments. Verify if verifyWebhook() returns true unconditionally in AlipayGateway.php.

Impact Analysis

An attacker could exploit this to create fraudulent transactions by sending fake payment notifications. This could lead to financial losses as orders are marked as paid without actual payment. The system would incorrectly record completed payments and update ledger entries, causing accounting discrepancies.

Compliance Impact

This vulnerability could lead to unauthorized transactions and incorrect financial records, violating data integrity and audit requirements in GDPR and HIPAA. It may also fail compliance checks for secure payment processing and financial reporting standards.

Mitigation Strategies

Disable the Alipay gateway if not in use. Update to the latest OwnPay version if available. Ensure alipay_public_key is configured and required. Remove fallback logic in verify() and verifyWebhook() methods. Block unauthenticated POST /webhook/{gateway} requests.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-76100. 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...