Read the docs
TI-2026-68958 Aliases CVE-2026-82212GHSA-8fcj-x85r-h3ff

Nexi XPay Build WordPress plugin accepts forged payment notifications

Priority LOW 38CWE-345Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
None · High · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-345.

Summary

The Nexi XPay Build WordPress plugin from 7.2.2 through 7.6.2 does not correctly verify the security token on its payment notification route (CWE-345). It accepts notifications for orders that have no stored token, so an unauthenticated remote attacker can mark arbitrary orders as paid or mark genuinely paid orders as failed. A public exploit is linked in the references.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00131 2nd percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownNexi XPay Build7.2.2 – 7.6.2—No fix listedCNA
  • Nexi XPay Build VendorUnknown Affected 7.2.2 – 7.6.2 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Nexi XPay Build.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-07 Threatist record created from CVE-2026-82212
  2. 2026-10-07 Alias added: GHSA-8fcj-x85r-h3ff
  3. 2026-10-07 Weakness changed · CISA ADP
  4. 2026-10-07 CISA SSVC decision points changed
  5. 2026-10-07 Priority changed: MEDIUM → LOW

References

Sources