Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 26 Oct 2026 14:15:00 +0100
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-20 CWE-285 CWE-330 |
Mon, 26 Oct 2026 12:30:00 +0100
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-287 | |
| Metrics |
cvssV3_1
|
Mon, 26 Oct 2026 09:45:00 +0100
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-20 CWE-285 CWE-330 |
Mon, 26 Oct 2026 07:30:00 +0100
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | OPay Payment Gateway for WooCommerce <= 2.5.5 - Unauthenticated Payment Confirmation Forgery via Empty Default Secret Key | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2026-10-26T10:13:35.664Z
Reserved: 2026-09-30T12:02:14.736Z
Link: CVE-2026-103319
Updated: 2026-10-26T10:05:04.491Z
Status : Deferred
Published: 2026-10-26T07:17:07.193
Modified: 2026-10-26T13:50:14.083
Link: CVE-2026-103319
No data.
OpenCVE Enrichment
Updated: 2026-10-26T14:00:14Z
-
CWE-287
Improper Authentication