CVE-2026-94299

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

GHSA-w5qf-7xj7-vf4x ↗EUVD-2026-92966 ↗

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.
elegro Crypto Payment <= 1.0.1
CWE-863 Incorrect Authorization
ETK-2026-736, permanent identifier
15d 05h 26msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h51m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

elegro Crypto Payment for WordPress through 1.0.1 can trust payment notifications without a configured shared secret. An unauthenticated attacker may forge confirmations and change order statuses when the shared secret remains empty or at its default value.

mitigation

Configure a non-empty, strong shared secret for payment notifications immediately and verify that notification handling enforces it. Restrict access to notification endpoints and monitor order-status changes until an updated plugin release is available.

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.16%5th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 06:00Z
Δ 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-06 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-736",
  "cve_id": "CVE-2026-94299",
  "display_id": "CVE-2026-94299",
  "ghsa_id": "GHSA-w5qf-7xj7-vf4x",
  "euvd_id": "EUVD-2026-92966",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated payment confirmation forgery in elegro Crypto Payment",
  "summary": "elegro Crypto Payment for WordPress through 1.0.1 can trust payment notifications without a configured shared secret. An unauthenticated attacker may forge confirmations and change order statuses when the shared secret remains empty or at its default value.",
  "mitigation": "Configure a non-empty, strong shared secret for payment notifications immediately and verify that notification handling enforces it. Restrict access to notification endpoints and monitor order-status changes until an updated plugin release is available.",
  "vendor": null,
  "product": "elegro Crypto Payment",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.0.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "elegro Crypto Payment",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 6.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
  "epss_score": 0.0016,
  "epss_percentile": 0.0532,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.632860683333334,
  "t0_at": "2026-10-06T06:00:20.974000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-06T06:00:20.974000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T06:00:20.974000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-94299"
    }
  }
}

published 2026-10-06 06:39Z
last change 2026-10-21 11:52Z

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.