Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33661: CWE-290: Authentication Bypass by Spoofing in yansongda pay

0
High
VulnerabilityCVE-2026-33661cvecve-2026-33661cwe-290
Published: Thu Mar 26 2026 (03/26/2026, 21:05:22 UTC)
Source: CVE Database V5
Vendor/Project: yansongda
Product: pay

Description

CVE-2026-33661 is a high-severity authentication bypass vulnerability in the yansongda pay SDK versions prior to 3. 7. 20. The flaw exists in the verify_wechat_sign() function, which skips signature verification if the HTTP Host header is set to 'localhost'. An attacker can exploit this by sending a crafted request with a 'Host: localhost' header to the WeChat Pay callback endpoint, bypassing RSA signature checks. This enables forging fake payment success notifications, causing applications to incorrectly mark orders as paid without actual transactions. The vulnerability affects open-source payment SDK integrations for Chinese payment services and has a CVSS score of 8. 6. No known exploits are reported in the wild yet. The issue is fixed in version 3.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/26/2026, 21:45:45 UTC

Technical Analysis

The vulnerability CVE-2026-33661 affects the yansongda pay SDK, an open-source payment extension widely used for integrating Chinese payment services such as WeChat Pay. The root cause lies in the verify_wechat_sign() function within src/Functions.php, which unconditionally bypasses signature verification when the PSR-7 HTTP request's Host header is set to 'localhost'. This logic flaw allows an attacker to craft an HTTP request to the WeChat Pay callback endpoint with a manipulated 'Host: localhost' header, causing the SDK to skip the critical RSA signature verification step. Consequently, the attacker can forge fake payment success notifications that the application trusts, leading to fraudulent order fulfillment without actual payment. The vulnerability is present in all versions before 3.7.20, where the issue has been corrected by enforcing proper signature verification regardless of the Host header. The CVSS 3.1 score of 8.6 reflects the network attack vector, no required privileges or user interaction, and the high impact on integrity with a scope change since the application’s trust boundary is compromised. Although no exploits have been publicly reported, the simplicity of the attack vector and the critical nature of payment processing make this a significant threat to affected applications.

Potential Impact

This vulnerability can have severe consequences for organizations relying on the yansongda pay SDK for WeChat Pay integrations. Attackers can bypass payment verification, causing applications to mark orders as paid without actual transactions, leading to direct financial losses and potential fraud. This undermines the integrity of payment systems, damages customer trust, and may result in chargebacks or legal liabilities. The scope of impact includes any e-commerce platforms, financial services, or applications using vulnerable versions of the SDK, especially those processing high volumes of transactions. Additionally, the breach of payment integrity can facilitate further fraudulent activities, including unauthorized access to services or goods. The lack of authentication or user interaction requirements makes exploitation straightforward for remote attackers, increasing the risk of widespread abuse if the vulnerability is not promptly addressed.

Mitigation Recommendations

Organizations should immediately upgrade the yansongda pay SDK to version 3.7.20 or later, where the vulnerability is fixed by enforcing signature verification regardless of the Host header. Until the upgrade is applied, implement strict validation of incoming HTTP Host headers at the web server or application firewall level to reject requests with 'localhost' or other suspicious values. Additionally, monitor payment callback endpoints for anomalous traffic patterns or unexpected Host headers. Employ network segmentation and access controls to limit exposure of payment callback endpoints to trusted sources only. Conduct thorough code reviews and security testing on payment processing logic to detect similar bypass conditions. Finally, maintain an incident response plan to quickly address any suspected fraudulent transactions resulting from this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-23T15:23:42.219Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69c5a54b3c064ed76fcfc828

Added to database: 3/26/2026, 9:29:47 PM

Last enriched: 3/26/2026, 9:45:45 PM

Last updated: 3/27/2026, 5:26:51 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses