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.
Metrics
Affected Vendors & Products
No data.
No data.
No data.
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
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
|
Projects
Sign in to view the affected projects.
MITRE
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2026-10-07T06:47:53.881Z
Reserved: 2026-08-28T08:30:59.212Z
Link: CVE-2026-82212
Vulnrichment
No data.
NVD
Status : Received
Published: 2026-10-07T07:17:01.493
Modified: 2026-10-07T07:17:01.493
Link: CVE-2026-82212
Redhat
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.