Quick answers
- Is CVE-2026-82212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82212 being exploited in the wild.
- How severe is CVE-2026-82212?
- High severity, with a CVSS score of 7.5, published 7 October 2026.
- Which products and versions are affected?
- Nexi XPay Build 7.2.2 through 7.6.2.
- Is there a fix for CVE-2026-82212?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82212 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-82212?
- Check whether you run Nexi XPay Build at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The plugin fails to validate security tokens on its payment notification route when the target order has no stored token, allowing unauthenticated attackers to craft requests that mark arbitrary orders as paid or mark legitimate paid orders as failed. This is an authentication bypass (CWE-287) on a critical payment processing function accessible over the network without prior authentication.
Affected products
- Nexi XPay Build 7.2.2 through 7.6.2
Timeline
- 2026-10-05: disclosed
- 2026-10-07: advisory