CVE-2026-103313 BitPay Gateway for WooCommerce <= 4.1.3 - Unauthenticated Payment Bypass via Payment Return Handler
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-103313 and fix it if it is affected.
What it is: CVE-2026-103313 is a medium-severity vulnerability in Unknown BitPay Gateway for WooCommerce, published on 28 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-103313 in the wild and no public exploit code.
Affected product: Unknown BitPay Gateway for WooCommerce. 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-103313/ (Markdown: https://insights.sbomify.com/CVE-2026-103313/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-103313?
CVE-2026-103313 is a medium-severity vulnerability in Unknown BitPay Gateway for WooCommerce, published on 28 Oct 2026.
Official description
The BitPay Gateway for WooCommerce WordPress plugin through 4.1.3 does not bind the payment provider's transaction confirmation to the order it completes, nor verify the confirmed amount, allowing an unauthenticated attacker who holds a single genuine low-value transaction to mark arbitrary higher-value orders as paid.
Weakness: CWE-345
Which versions are affected by CVE-2026-103313?
How do I fix CVE-2026-103313?
No fix has been published for CVE-2026-103313 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-103313 being exploited?
There is no known exploitation of CVE-2026-103313 in the wild and no public exploit code.
Sources
Also known as GHSA-m8g2-r2r9-qg3j.