Is CVE-2026-82211 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-82211 being exploited in the wild.

How severe is CVE-2026-82211?

High severity, with a CVSS score of 8.2, published 7 October 2026.

Which products and versions are affected?

Nexi XPay Build 7.0.0 through 7.6.2.

Is there a fix for CVE-2026-82211?

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-82211 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-82211?

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.

CVE-2026-82211: Nexi XPay Build WordPress plugin missing authorization in payment routes

CVE-2026-82211 · Severity: high · CVSS 8.2 · Published 2026-10-07

The Nexi XPay Build plugin, which processes payments for WooCommerce stores, fails to verify payment confirmation requests on unauthenticated endpoints. Attackers can exploit this to fraudulently mark orders as paid, cancel legitimate transactions, or retrieve customer details from guest orders without any credentials.

Technologies: Nexi XPay Build. Vendors: Nexi.

Quick answers

Is CVE-2026-82211 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82211 being exploited in the wild.
How severe is CVE-2026-82211?: High severity, with a CVSS score of 8.2, published 7 October 2026.
Which products and versions are affected?: Nexi XPay Build 7.0.0 through 7.6.2.
Is there a fix for CVE-2026-82211?: 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-82211 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-82211?: 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 exposes multiple unauthenticated routes that accept payment result parameters without proper verification or authorization checks (CWE-862). An attacker can send crafted requests to these endpoints over the network to modify arbitrary order statuses, cancel transactions, and disclose order keys containing guest customer information. No fix is currently available.

Affected products

Nexi XPay Build 7.0.0 through 7.6.2

Timeline

2026-10-05: disclosed
2026-10-07: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.