CVE-2026-103319 The OPay Payment Gateway for WooCommerce WordPress plugin through 2.5.5 does not properly verify that payment notifications originate from t
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-103319 and fix it if it is affected.
What it is: CVE-2026-103319 is a medium-severity vulnerability in Unknown OPay Payment Gateway for WooCommerce, published on 26 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-103319 in the wild and no public exploit code.
Affected product: Unknown OPay Payment 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-103319/ (Markdown: https://insights.sbomify.com/CVE-2026-103319/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-103319?
CVE-2026-103319 is a medium-severity vulnerability in Unknown OPay Payment Gateway for WooCommerce, published on 26 Oct 2026.
Official description
The OPay Payment Gateway for WooCommerce WordPress plugin through 2.5.5 does not properly verify that payment notifications originate from the payment provider, as the secret used to validate their signature is empty by default, allowing unauthenticated attackers to forge a valid notification and mark arbitrary orders as paid, cancelled or failed.
Weakness: CWE-287
Which versions are affected by CVE-2026-103319?
How do I fix CVE-2026-103319?
No fix has been published for CVE-2026-103319 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-103319 being exploited?
There is no known exploitation of CVE-2026-103319 in the wild and no public exploit code.
Sources
Also known as GHSA-4xm4-56qr-w7fc.