Nexi XPay: A security weakness
Nexi XPay is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 8.3.0.
- Component
- Nexi XPay
- Plugin slug
cartasi-x-pay- Affected
- <= 8.3.0
- Safe version
> 8.3.0- Published
- Apr 14, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Apr 14, 2026 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update Nexi XPay to a release after 8.3.0, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Nexi XPay plugin for WordPress is vulnerable to unauthorized modification of data due to missing authorization checks on the redirect function in all versions up to, and including, 8.3.0. This makes it possible for unauthenticated attackers to mark pending WooCommerce orders as paid/completed.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N