WordPress security by component

Nexi XPay Build

Nexi XPay Build (nexi-xpay-build) is a WordPress plugin with 3 published CVE records in this archive. The latest tracked vulnerability was published Oct 07, 2026; the highest published CVSS base score is 8.2.

Plugin slug: nexi-xpay-build

Latest vulnerability

CVE-2026-82212: Nexi XPay Build: Missing order token permits forged payment notifications

An unauthenticated attacker can submit a payment notification for an order that has no stored security token. The notification route accepts that missing-token condition instead of rejecting it, allowing arbitrary orders to be marked paid or genuinely paid orders to be marked failed. The route and token parameter names are undisclosed. Affected versions: 7.2.2 through 7.6.2. No fixed release is confirmed.

PublishedOct 07, 2026

Safe version guidanceSee mitigation notes

Published vulnerabilities for nexi-xpay-build
		Safe version
Oct 07, 2026	CVE-2026-82212 Nexi XPay Build: Missing order token permits forged payment notifications An unauthenticated attacker can submit a payment notification for an order that has no stored security token. The notification route accepts that missing-token condition instead of rejecting it, allowing arbitrary orders to be marked paid or genuinely paid orders to be marked failed. The route and token parameter names are undisclosed. Affected versions: 7.2.2 through 7.6.2. No fixed release is confirmed.	See mitigation notes	CVE7.5
Oct 07, 2026	CVE-2026-82211 Nexi XPay Build: Unverified results alter orders and expose guest details An unauthenticated attacker can supply an unverified payment result to several public routes. The plugin trusts that result to mark orders paid or failed, cancel them, and disclose order keys that expose guest buyer details. The exact route names and request fields are undisclosed. Affected versions: 7.0.0 through 7.6.2. No fixed release is confirmed.	See mitigation notes	CVE8.2
Sep 11, 2026	CVE-2026-82213 Nexi XPay Build exposes other customers' saved payment tokens Nexi XPay Build versions 7.6.1 through 7.6.2 do not verify that a requested saved payment token belongs to the current user. An unauthenticated attacker can retrieve another customer's stored card-token reference together with a valid authorization signature. The authoritative export does not identify the endpoint, token identifier parameter, customer binding, or signing function.	See mitigation notes	CVE5.3

Data attribution: This product uses the NVD API but is not endorsed or certified by the NVD.

Vulnerability data licensing

CVE. Copyright © 1999–2026, The MITRE Corporation. MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE™). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

CWE. Copyright © 2006–2026, The MITRE Corporation. CWE™ is free to use by any organization or individual for any research, development, and/or commercial purposes, per these CWE Terms of Use. Accordingly, The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. Any copy you make for such purposes is authorized on the condition that you reproduce MITRE’s copyright designation and this license in any such copy.

CVSS. CVSS is owned and managed by FIRST.Org, Inc. (FIRST) and used by permission.

Source-record text is CVE/CNA content delivered through the NVD API. Fused summaries and remediation guidance are independently authored and are not attributed to NVD.

All other copyrights and trademarks are the property of their respective owners.

Full data sources, terms, and disclaimers