CVE-2026-33661 — Vulnerability in yansongda/pay — CVE Details
WeChat Pay callback signature verification bypassed when Host header is localhost
Summary
Advisory Timeline
- First published March 25, 2026 (201 days ago).
- Last revised March 27, 2026 — 2 days after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
composer require "yansongda/pay:^3.7.20"
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (1)
Affects 1 ecosystem: packagist (1).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| yansongda/pay | packagist | v0.5.0, v0.5.1, v0.5.2, v0.5.3 (+249 more) | 3.7.20 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-290
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 8.6 score means for each attack dimension.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
References
- https://github.com/yansongda/pay/security/advisories/GHSA-q938-ghwv-8gvcWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-33661ADVISORY
- https://github.com/yansongda/pay/commit/26987ebf789f1e7f0a85febb640986ab4289fd7fWEB
- https://github.com/yansongda/payPACKAGE
- https://github.com/yansongda/pay/releases/tag/v3.7.20WEB
Frequently Asked Questions
- What is CVE-2026-33661?
- WeChat Pay callback signature verification bypassed when Host header is localhost This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.6/10).
- How do I check if my project is affected by CVE-2026-33661?
- CVE-2026-33661 affects yansongda/pay. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-33661 and 200,000+ other known vulnerabilities.
Severity & Exploitability
High exploitability or significant impact. Prioritize remediation within days.
Also Known As
Related CVEs
- CVE-2026-65954HIGH
PHPCSUtils: Remote code execution via eval() in AbstractArrayDeclarationSniff::getActualArrayKey()
- CVE-2026-61825HIGH
code16/sharp has a stored XSS via data-html-content Sanitizer Bypass
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies