← Back to search

CVE-2026-82212

7.5 HIGH

Published 2026-10-07 · Updated 2026-10-07

AI risk analysis

Summary
The Nexi XPay WordPress plugin fails to validate security tokens on its payment notification endpoint, allowing unauthenticated attackers to mark any order as paid or failed by exploiting a missing token validation check.
Exploitability
Exploitation is straightforward with no prerequisites; attackers only need to send a specially crafted request to the payment notification route without needing authentication or valid tokens.
Blast radius
The impact could be significant across all orders processed through the vulnerable plugin, potentially allowing unauthorized revenue recognition and order status manipulation for any customer who has made a purchase.
Detection
No reliable host or network indicator is derivable from the published description.
Prioritized remediation
Upgrade to version 7.6.3 or later which includes the security token validation fix for the payment notification route.
paymentorderwordpress

Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.

NVD 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.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Weaknesses

CWE-345

All references

Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.

Related CVEs

Related by shared AI tags and CWE weakness class. Browse the full archive.