Skip to main content

CVE-2026-82213: CWE-639 Authorization Bypass Through User-Controlled Key in Nexi XPay Build

0
Medium
VulnerabilityCVE-2026-82213cvecve-2026-82213cwe-639
Published: 09/11/2026 (09/11/2026, 10:56:34 UTC)
Source: CVE Database V5
Product: Nexi XPay Build

Description

The Nexi XPay Build WordPress plugin from 7.6.1 to 7.6.2 does not verify that the saved payment token being requested belongs to the current user, allowing unauthenticated attackers to retrieve other customers' stored card token references together with a valid authorisation signature.

CVSS v3.1

Score 5.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected software

Nexi XPay Build

Affected versions
>=7.6.1 <=7.6.2

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/11/2026, 11:18:14 UTC

Technical Analysis

CVE-2026-82213 is an authorization bypass vulnerability in the Nexi XPay Build WordPress plugin versions 7.6.1 and 7.6.2. The plugin does not properly verify ownership of saved payment tokens when they are requested, enabling unauthenticated attackers to access other users' stored card token references with a valid authorization signature. This issue is categorized under CWE-639 (Authorization Bypass Through User-Controlled Key). No patch or remediation details are provided in the available data.

Potential Impact

An unauthenticated attacker can retrieve stored card token references belonging to other customers. This exposure could lead to unauthorized access to sensitive payment token data, potentially facilitating fraudulent transactions or further attacks. The confidentiality of stored payment tokens is compromised, but integrity and availability are not impacted according to the CVSS vector.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the plugin's endpoints and monitor for suspicious activity related to payment token requests. Avoid exposing saved payment token references to unauthenticated users.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2026-08-28T08:31:02.009Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6aa3dff291cc7f3848109ff6

Added to database: 09/11/2026, 11:03:14 UTC

Last enriched: 09/11/2026, 11:18:14 UTC

Last updated: 09/11/2026, 14:27:55 UTC

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses