CVE-2026-82211
Unauthenticated order-status manipulation in Nexi XPay Build WordPress plugin.
Is CVE-2026-82211 being exploited?
Not confirmed. CVE-2026-82211 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-82211?
CVE-2026-82211 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82211?
Not known from our data. No patch reference has been recorded for CVE-2026-82211, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-82211 affect?
CVE-2026-82211 affects Nexi XPay Build WordPress plugin <= 7.6.2, WordPress e-commerce sites using Nexi XPay Build. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82211?
Patch ASAP when vendor releases; block/validate payment-result endpoints and audit recent orders.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can mark orders paid/failed, cancel orders, and retrieve guest order keys exposing buyer details.
Immediate action required
- affected>= 7.0.0 and <= 7.6.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.