CVE-2026-110285 WP Stripe Checkout < 1.2.2.62 - Unauthenticated Forged Payment Completion via an Unset Webhook Signing Secret
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-110285 and fix it if it is affected.
What it is: CVE-2026-110285 is a medium-severity vulnerability in Unknown WP Stripe Checkout, published on 25 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-110285 in the wild and no public exploit code.
Affected product: Unknown WP Stripe Checkout. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-110285/ (Markdown: https://insights.sbomify.com/CVE-2026-110285/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-110285?
CVE-2026-110285 is a medium-severity vulnerability in Unknown WP Stripe Checkout, published on 25 Oct 2026.
Official description
The WP Stripe Checkout WordPress plugin before 1.2.2.62 does not verify the Stripe webhook signature when no signing secret is configured, which is its default state, allowing unauthenticated attackers to forge a payment completion notification and create a completed order without paying.
Weakness: CWE-287
Which versions are affected by CVE-2026-110285?
How do I fix CVE-2026-110285?
No fix has been published for CVE-2026-110285 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-110285 being exploited?
There is no known exploitation of CVE-2026-110285 in the wild and no public exploit code.
Sources
Also known as GHSA-vq2h-2cv6-5rpj.