Vulnerability in Nexi Xpay Build
CVE-2026-82212
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
EPSS exploit prediction
EPSS: 0.001 (2.3th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 2nd percentile — 2.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
The 30-day trend appears once there are two daily scores.
Affected products
- Nexi Xpay Build
Weakness classification (CWE)
References
- wpscan.com/vulnerability/66df6adb-336c-4660-9a63-5e6e550a2edb/ (technical-description, exploit, vdb-entry)
Frequently asked questions
- What is CVE-2026-82212?
- CVE-2026-82212 is a high-severity vulnerability in Nexi Xpay Build, classified under Insufficient Verification of Data Authenticity. CVSS score: 7.5/10. Published 2026-10-07.
- How severe is CVE-2026-82212?
- High severity. CVSS v3 base score is 7.5 out of 10.