Unauthenticated order manipulation via unchecked payment results
Published Oct 7, 2026 · Updated Oct 7, 2026
Payment-result validation failure in Nexi XPay Build 7.0.0 through 7.6.2 allows remote attackers to alter WooCommerce orders. Several unauthenticated payment-result routes accept a supplied outcome without verifying it before updating an order or returning its key. On a reachable merchant site, forged results can mark arbitrary orders paid or failed or cancel them, while disclosed order keys expose guest buyers' details.
Summary
What happened
Payment-result validation failure in Nexi XPay Build 7.0.0 through 7.6.2 allows remote attackers to alter WooCommerce orders. Several unauthenticated payment-result routes accept a supplied outcome without verifying it before updating an order or returning its key. On a reachable merchant site, forged results can mark arbitrary orders paid or failed or cancel them, while disclosed order keys expose guest buyers' details.
The record
- CVE
- CVE-2026-82211
- Published
- Oct 7, 2026
- Updated
- Oct 7, 2026
- Vendor
- Nexi
- Product
- Nexi XPay Build
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 7, 2026CVE publishedPublication date reported by the CVE source.
- Oct 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.0.0 <=7.6.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started