Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-82211 – Unauthenticated Payment Manipulation & Order Data Disclosure – Nexi XPay Build Word

Be the first to know when new zero-days emerge:

Summary

CVE-2026-82211 is a missing authorization vulnerability (CWE-862) in the Nexi XPay Build WordPress plugin, which integrates the Nexi XPay payment gateway into WordPress/WooCommerce sites. The plugin fails to validate the payment result supplied to several of its unauthenticated routes, allowing unauthenticated attackers to fraudulently change order payment statuses and retrieve order keys that expose guest customer information. The flaw is rated High severity with a CVSS v3.1 base score of 8.2.

Technical details

  • Root cause: several of the plugin’s HTTP routes that process payment results do not require authentication and do not verify that the submitted payment result/order data actually originates from Nexi’s payment gateway.
  • Trigger condition: an attacker sends crafted requests to these unauthenticated routes, referencing an order, without needing valid credentials or prior interaction with the site.
  • Attack vector: network-based (AV:N), low attack complexity (AC:L), no privileges (PR:N) and no user interaction (UI:N) required.
  • Impact: attackers can mark arbitrary orders as paid or failed, cancel transactions, and obtain order keys — enabling fraudulent order completion/cancellation and disclosure of guest customers’ order details (low confidentiality impact, high integrity impact, no availability impact).

Affected software

  • Nexi XPay Build WordPress plugin, versions 7.0.0 through 7.6.2

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Mitigation and recommended actions

  • Immediate: As of publication, no patched version of the Nexi XPay Build plugin has been released. Site administrators should monitor the official WordPress.org plugin page and Nexi vendor channels for a security update and apply it as soon as it becomes available.
  • If no patch: Consider temporarily deactivating the Nexi XPay Build plugin on sites where payment-order integrity is business-critical, restrict access to the plugin’s payment-notification/result endpoints at the web server or WAF layer to only the legitimate Nexi gateway IP ranges, and monitor order logs for unexpected payment status changes or cancellations.

References

Get a free Attack Surface scan to see if you’re exposed.

Get a free Attack Surface scan to see if you’re exposed.

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge