# CVE-2026-82211: Nexi XPay Build <= 7.6.2 - Unauthenticated Payment Completion and Order Key Disclosure

> Attackers can manipulate order statuses and expose guest buyer details via unauthenticated routes in the Nexi XPay Build WordPress plugin.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-65w5-qcwh-f3g3

## What is CVE-2026-82211?

CVE-2026-82211 is a high-severity missing authorization vulnerability in Unknown Nexi XPay Build, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Nexi XPay Build WordPress plugin through 7.6.2 does not verify the payment result supplied to several of its unauthenticated routes, allowing attackers to mark arbitrary orders as paid or failed, to cancel them, and to obtain order keys which expose guest buyers' details.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-82211?


## How do I fix CVE-2026-82211?

No fix has been published for CVE-2026-82211 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82211 being exploited?

There is no known exploitation of CVE-2026-82211 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82211 and fix it if it is affected.

What it is: CVE-2026-82211 is a high-severity missing authorization vulnerability in Unknown Nexi XPay Build, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82211 in the wild and no public exploit code.

Affected product: Unknown Nexi XPay Build. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82211/ (Markdown: https://insights.sbomify.com/CVE-2026-82211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82211
- OSV: https://osv.dev/vulnerability/CVE-2026-82211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82211/
Summaries are generated and may contain mistakes; the official description above is the record.