Nexi XPay Build
nexi-xpay-build · plugin
Known security vulnerabilities for Nexi XPay Build. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
3 exploitable without logging in · latest Oct 7, 2026
Before you install
Do not install
- Closed on wordpress.org on Aug 31, 2026; no updates will come.
- 3 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Closed on wordpress.org
Removed from the directory on Aug 31, 2026 · reason: author request. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 21, 2026
Vulnerabilities
- High 8.2
CVE-2026-82211unauthenticated≤ 7.6.2
Nexi XPay Build <= 7.6.2 - Unauthenticated Payment Completion and Order Key Disclosure
- High 7.5
CVE-2026-82212unauthenticated≤ 7.6.2
Nexi XPay Build <= 7.6.2 - Unauthenticated Payment Bypass via NPG Notification Handler
- Medium 5.3
CVE-2026-82213unauthenticated≤ 7.6.2
Nexi XPay Build 7.6.1 - 7.6.2 - Unauthenticated Saved Payment Token Disclosure via IDOR
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).