CVE-2026-82213

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-11. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 11, 2026

Advisory Details (1)

Auto-updated Sep 11, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Nexi XPay Build 7.6.1 – 7.6.2 – Unauthenticated Saved Payment Token Disclosure via IDOR | CVE 2026-82213 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/ccdf87ac-7442-441f-ad96-466c715b1d66/

Vendor Advisories for CVE-2026-82213(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-21 02:53 UTCEG score recompute
  2. 2026-09-21 02:53 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-20 04:23 UTCEG score recompute
  5. 2026-09-20 04:23 UTCGHSA enrichment
  6. 2026-09-19 05:53 UTCEG score recompute
  7. 2026-09-19 05:53 UTCGHSA enrichment
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-18 07:24 UTCEG score recompute
  10. 2026-09-18 07:24 UTCGHSA enrichment
  11. 2026-09-17 08:54 UTCEG score recompute
  12. 2026-09-17 08:54 UTCGHSA enrichment
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 10:24 UTCEG score recompute
  15. 2026-09-16 10:24 UTCGHSA enrichment
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 11:54 UTCEG score recompute
  18. 2026-09-15 11:54 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 13:24 UTCEG score recompute
  22. 2026-09-14 13:24 UTCGHSA enrichment
  23. 2026-09-13 14:54 UTCGHSA enrichment
  24. 2026-09-12 16:24 UTCEG score recompute
  25. 2026-09-12 16:24 UTCGHSA enrichment
Show 7 more
  1. 2026-09-11 17:53 UTCGHSA enrichment
  2. 2026-09-11 13:23 UTCEG score recompute
  3. 2026-09-11 13:23 UTCGHSA enrichment
  4. 2026-09-11 12:20 UTCEG score recompute
  5. 2026-09-11 11:26 UTCEG score recompute
  6. 2026-09-11 11:00 UTCEG score recompute
  7. 2026-09-11 10:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82213?
CVE-2026-82213 is a medium vulnerability published on September 11, 2026. 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.
When was CVE-2026-82213 disclosed?
CVE-2026-82213 was first published in the National Vulnerability Database on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82213 actively exploited?
CVE-2026-82213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.7% of all scored CVEs.
What is the CVSS score of CVE-2026-82213?
CVE-2026-82213 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-82213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82213, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82213

Explore →

Is Your Infrastructure Affected by CVE-2026-82213?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs