CVE-2026-82212

Nexi XPay Build <= 7.6.2 - Unauthenticated Payment Bypass via NPG Notification Handler

Published Oct 7, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Nexi XPay Build WordPress plugin versions up to 7.6.2 accept payment notification requests without correctly validating the security token; when the target order has no stored token, any requester can trigger a status change. An attacker who crafts such a notification can mark an unpaid order as paid or force a legitimately paid order to fail, resulting in unauthorized fund transfers or order cancellations. The vulnerability permits the attacker to alter the financial status of any order on the site without authentication, and thus it directly compromises the integrity of transaction data.

Affected Systems

WordPress sites that have installed the Nexi XPay Build plugin with a version 7.6.2 or earlier. The attack exploits the payment notification endpoint exposed by the plugin, which is accessible to all users, including unauthenticated visitors.

Risk and Exploitability

The CVSS score for this issue is 7.5, indicating a high severity The EPSS score is unavailable, but the exploit is straightforward: sending a synthetic payment notification request with an unsigned or missing token to the plugin’s endpoint. The vulnerability is not listed in the CISA KEV catalog, though its impact could be wide in e‑commerce deployments. Attackers could easily automate notification requests, and because no authentication is required, the window for exploitation is continuously open until patched. Organizations running affected WordPress sites should treat this as a high‑risk flaw that should be remediated promptly.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Nexi XPay Build plugin to a version newer than 7.6. restored.
  • If an immediate update is not possible, disable or restrict access to the payment notification endpoint, for example by enabling IP whitelisting or by confirming the request originates from the payment gateway’s known IP ranges.
  • Add a server‑side check to verify the presence and validity of the security token before changing the order status, and log all status‑change events to detect suspicious activity.

Generated by OpenCVE AI on October 7, 2026 at 13:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions nexi Xpay Build
Vendors & Products Wordpress-extensions
Wordpress-extensions nexi Xpay Build
Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
Weaknesses CWE-345
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
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.
Title Nexi XPay Build <= 7.6.2 - Unauthenticated Payment Bypass via NPG Notification Handler
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 7, 2026, 9:47 AM
Reserved
Aug 28, 2026, 8:30 AM
Status
Deferred
Published
Oct 7, 2026, 7:17 AM
Modified
Oct 7, 2026, 2:52 PM