Get real-time updates on Telegram
CVE-2026-82212: Nexi XPay Build 7.2.2 through 7.6.2
CVE-2026-82212. CVSS 3.1 base score 7.5 (HIGH, Vendor/CNA).
Affected technology
Nexi XPay Build · 7.2.2 through 7.6.2
Vendor not specified by the source
Description’s affected range: through 7.6.2 does not correctly validate the security token on its payment notification route
Component: Not specified by the source
Attack conditions (Vendor/CNA, CVSS 3.1): Network (remote) · No privileges required · No user interaction required
What an attacker can do
The source says 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. Vendor/CNA’s CVSS 3.1 assessment (base score 7.5/10) rates confidentiality and availability impact as none; integrity impact as high.
- CWE
- CWE-345
- CCR priority
- 30.0 /100 (P4)
- CVSS 3.1
- 7.5 /10 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N · Vendor/CNA
- KEV
- no
Provenance
- GitHub Advisory Database · Source record · observed 2026-10-07 13:20:35.851963+00:00 UTC
- NVD CVE API 2.0 · Source record · observed 2026-10-07 15:14:18.222433+00:00 UTC
Stable permalink: https://cybercodered.org/item/cve-cve-2026-82212.html