{"answers":{"affected":"2 open source packages ship an affected version, including yansongda/pay. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33661 exists.","fix":"Upgrade yansongda/pay to 3.7.20 or later.","what":"CVE-2026-33661 is a high-severity vulnerability in yansongda pay, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33661 and fix it if it is affected.\n\nWhat it is: CVE-2026-33661 is a high-severity vulnerability in yansongda pay, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33661 exists.\n\nAffected packages and fixed versions:\n- yansongda/pay (Packagist): affected all versions; fixed in 3.7.20\n- yansongda/pay (Packagist): affected all versions; fixed in 3.7.20\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33661/ (Markdown: https://insights.sbomify.com/CVE-2026-33661/index.md)","id":"CVE-2026-33661","markdown":"https://insights.sbomify.com/CVE-2026-33661/index.md","name":"CVE-2026-33661","record":{"aliases":["GHSA-q938-ghwv-8gvc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WeChat Pay SDK","requires_auth":"none","summary":"Attackers can bypass signature verification by spoofing the Host header, allowing them to forge payment success notifications and mark orders as paid without actual payment.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pay","vendor":"yansongda"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"WeChat Pay callback signature verification bypassed when Host header is localhost","id":"CVE-2026-33661","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"OP-TEE: RSASSA EMSA- PKCS1-v1_5 underflow in emsa_pkcs1_v1_5_encode()","id":"CVE-2026-33662"},"packages":[{"ecosystem":"Packagist","fixed":["3.7.20"],"introduced":["0"],"last_affected":[],"package":"yansongda/pay","purl":null,"source":"GHSA-q938-ghwv-8gvc"},{"ecosystem":"Packagist","fixed":["3.7.20"],"introduced":["0"],"last_affected":[],"package":"yansongda/pay","purl":"pkg:composer/yansongda/pay","source":"GHSA-q938-ghwv-8gvc"}],"prev":{"headline":"n8n Has Multiple Remote Code Execution Vulnerabilities in Merge Node AlaSQL SQL Mode","id":"CVE-2026-33660"},"products":["pay"],"published":"2026-03-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-27","vendors":["yansongda"]},"summary":"Attackers can bypass signature verification by spoofing the Host header, allowing them to forge payment success notifications and mark orders as paid without actual payment.","url":"https://insights.sbomify.com/CVE-2026-33661/"}