CVE-2026-82212

waiting for further signalsZero needs more public information before it can validate it.

GHSA-8fcj-x85r-h3ff ↗EUVD-2026-94196 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Nexi XPay Build >= 7.2.2, <= 7.6.2
ETK-2026-856, permanent identifier
9d 09h 25msince last run
40mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+108h37m
0
+2h
+4h
+6h
+8h
+10h

description

Nexi XPay Build for WordPress through 7.6.2 improperly verifies payment-notification requests for orders without a stored security token. An unauthenticated attacker may alter affected orders' payment status. Exposure requires the attacker to reach the plugin's payment-notification route and target an order with no stored token.

mitigation

Restrict access to the payment-notification route to trusted payment-provider infrastructure until an updated plugin release is available. Review orders lacking stored payment tokens and verify their payment status.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.13%2nd percentile
agent run time
40m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 06:47Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-07 06:47Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-82212

{
  "etk_id": "ETK-2026-856",
  "cve_id": "CVE-2026-82212",
  "display_id": "CVE-2026-82212",
  "ghsa_id": "GHSA-8fcj-x85r-h3ff",
  "euvd_id": "EUVD-2026-94196",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Nexi XPay Build payment notifications",
  "summary": "Nexi XPay Build for WordPress through 7.6.2 improperly verifies payment-notification requests for orders without a stored security token. An unauthenticated attacker may alter affected orders' payment status. Exposure requires the attacker to reach the plugin's payment-notification route and target an order with no stored token.",
  "mitigation": "Restrict access to the payment-notification route to trusted payment-provider infrastructure until an updated plugin release is available. Review orders lacking stored payment tokens and verify their payment status.",
  "vendor": null,
  "product": "Nexi XPay Build",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.2.2, <= 7.6.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Nexi XPay Build",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
  "epss_score": 0.0013,
  "epss_percentile": 0.0243,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 40.21381206666667,
  "t0_at": "2026-10-07T06:47:53.881000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T06:47:53.881000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T06:47:53.881000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-82212"
    }
  }
}

published 2026-10-07 08:23Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.