CVE-2026-81648

validatedZero produced an exploit or a check.

GHSA-9r3q-6qw8-8pm7 ↗EUVD-2026-77085 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.+50d
CryptoPayment Gateway >= 1.2.1, <= 1.2.2
ETK-2026-3318Zero's internal tracking ID, independent of the CVE number., permanent identifier
+50dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−49dpublic poctrigger signal +0dcheck available+0.9dkev+1.0dagent stopped
−40d
−30d
−20d
−10d

description

CryptoPayment Gateway WordPress plugin versions 1.2.1 through 1.2.2 expose an AJAX endpoint without an authorization check. An unauthenticated remote attacker can perform administrative actions, potentially delete server files, alter payment-gateway settings, or retrieve stored wallet credentials. Exploitation requires the affected plugin to be installed and its vulnerable endpoint to be reachable.

mitigation

Disable and remove the affected CryptoPayment Gateway plugin from WordPress sites until a vendor-fixed release is available. Restrict public access to the affected AJAX endpoint and rotate any wallet credentials that may have been exposed.

check
available
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.
deterministic
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.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-13 20:06Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+0m
Δ to kevAttacks confirmed in the real world.
+50d

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-09-13 20:06Z
  2. 2026-11-02
    vulncheck_kev: trigger signal, started the run
  3. 2026-11-02 00:00Z
  4. 2026-11-02 22:10Z
  5. 2026-11-02 22:19Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3318",
  "cve_id": "CVE-2026-81648",
  "display_id": "CVE-2026-81648",
  "ghsa_id": "GHSA-9r3q-6qw8-8pm7",
  "euvd_id": "EUVD-2026-77085",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in CryptoPayment Gateway AJAX endpoint",
  "summary": "CryptoPayment Gateway WordPress plugin versions 1.2.1 through 1.2.2 expose an AJAX endpoint without an authorization check. An unauthenticated remote attacker can perform administrative actions, potentially delete server files, alter payment-gateway settings, or retrieve stored wallet credentials. Exploitation requires the affected plugin to be installed and its vulnerable endpoint to be reachable.",
  "mitigation": "Disable and remove the affected CryptoPayment Gateway plugin from WordPress sites until a vendor-fixed release is available. Restrict public access to the affected AJAX endpoint and rotate any wallet credentials that may have been exposed.",
  "vendor": "CryptoPayment Gateway",
  "product": "CryptoPayment Gateway",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.2.1, <= 1.2.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "CryptoPayment Gateway",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 10,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.010263533333333333,
  "t0_at": "2026-09-13T20:06:35.224000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-02T22:10:38.786938+00:00",
      "days": 50.086152348819446,
      "is_lower_bound": false,
      "measured_at": "2026-09-13T20:06:35.224000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-11-02T00:00:00+00:00",
      "days": 50,
      "is_lower_bound": false,
      "measured_at": "2026-09-13T20:06:35.224000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-81648"
    },
    "public_poc": {
      "at": "2026-09-13T20:06:35.224000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-13T20:06:35.224000+00:00",
      "url": "https://wpscan.com/vulnerability/9b1490a0-1381-4d22-8086-f75aade4e898/"
    },
    "trigger_signal": {
      "at": "2026-11-02T00:00:00+00:00",
      "days": 49.162092314814814,
      "is_lower_bound": false,
      "measured_at": "2026-09-13T20:06:35.224000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-81648"
    }
  }
}

published 2026-11-02 22:10Z
last change 2026-11-02 23:24Z

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.