Is yansongda/pay 2.8 vulnerable?

Composer · 7 releases from 2.8.0 to 2.8.6 · latest yansongda/pay is 3.7.20 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. yansongda/pay 2.8.6, the last 2.8 release, is affected by 1 known security advisory (1 high), including CVE-2026-33661. Upgrade to 3.7.20 or later to fix all of them.

Upgrade with:composer require yansongda/pay:^3.7.20

Is your project on an affected yansongda/pay?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting yansongda/pay 2.8.6

  • HighCVE-2026-33661GHSA-q938-ghwv-8gvc25 Mar 2026

    WeChat Pay callback signature verification bypassed when Host header is localhost

    Affected
    <3.7.20
    Fixed in
    3.7.20

Every yansongda/pay 2.8.x release

Affected: 2.8.0 to 2.8.6. Latest yansongda/pay: 3.7.20.

VersionKnown advisories
yansongda/pay 2.8.6CVE-2026-33661
yansongda/pay 2.8.5CVE-2026-33661
yansongda/pay 2.8.4CVE-2026-33661
yansongda/pay 2.8.3CVE-2026-33661
yansongda/pay 2.8.2CVE-2026-33661
yansongda/pay 2.8.1CVE-2026-33661
yansongda/pay 2.8.0CVE-2026-33661

Which of your client projects are still on yansongda/pay 2.8?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact yansongda/pay version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other yansongda/pay versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.