Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 07 Oct 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-285 |
Wed, 07 Oct 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-345 | |
| Metrics |
ssvc
|
Wed, 07 Oct 2026 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-285 |
Wed, 07 Oct 2026 07:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Nexi XPay Build WordPress plugin through 7.6.2 does not correctly validate the security token on its payment notification route, accepting the request when the target order has no stored token, which allows unauthenticated attackers to mark arbitrary orders as paid, or to mark genuinely paid orders as failed. | |
| Title | Nexi XPay Build <= 7.6.2 - Unauthenticated Payment Bypass via NPG Notification Handler | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2026-10-07T09:47:48.247Z
Reserved: 2026-08-28T08:30:59.212Z
Link: CVE-2026-82212
Updated: 2026-10-07T09:47:43.635Z
Status : Deferred
Published: 2026-10-07T07:17:01.493
Modified: 2026-10-07T14:52:43.420
Link: CVE-2026-82212
No data.
OpenCVE Enrichment
Updated: 2026-10-07T14:00:17Z