Pay is an open-source payment SDK extension package for various Chinese payment services. Prior to version 3.7.20, the verify_wechat_sign() function in src/Functions.php unconditionally skips all signature verification when the PSR-7 request reports localhost as the host. An attacker can exploit this by sending a crafted HTTP request to the WeChat Pay callback endpoint with a Host: localhost header, bypassing the RSA signature check entirely. This allows forging fake WeChat Pay payment success notifications, potentially causing applications to mark orders as paid without actual payment. Version 3.7.20 fixes the issue.
CVE-2026-33661
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 42%
- KEV
- Not listed
Published
March 26, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 2, 2026WeChat Pay callback signature verification bypassed when Host header is localhost · Advisory · yansongda/pay · GitHub
https://github.com/yansongda/pay/security/advisories/GHSA-q938-ghwv-8gvcv3.7.20
Patch available: yansongda/pay v3.7.20
https://github.com/yansongda/pay/releases/tag/v3.7.20commit 26987ebf789f (yansongda/pay)
Patch available: yansongda/pay v3.7.20 (contains commit 26987ebf789f)
https://github.com/yansongda/pay/commit/26987ebf789f1e7f0a85febb640986ab4289fd7fAffected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| yansongda/pay | v0.5.0 ... v3.7.9 (253 versions) | 3.7.20 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 29× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-02 13:14 UTCOSV refresh
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
Show 39 moreShow fewer
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 10:04 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 06:23 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 20:40 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 20:48 UTCEG score recompute
- 2026-08-11 03:50 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 16:54 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 05:56 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 03:20 UTCEG score recompute
- 2026-08-06 18:45 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 00:49 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 23:14 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 15:15 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:20 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-33661?
When was CVE-2026-33661 disclosed?
Is CVE-2026-33661 actively exploited?
What is the CVSS score of CVE-2026-33661?
How do I remediate CVE-2026-33661?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33661
Is Your Infrastructure Affected by CVE-2026-33661?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.