CVE-2026-76792

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

GHSA-gmxr-g9qg-qjhg ↗EUVD-2026-124289 ↗

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.
User Verification by PickPlugins >= 2.0.38, < 2.0.49
fixed in 2.0.49
ETK-2026-4250Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 06msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h46m
0
+4h
+6h
+8h
+10h
+12h

description

User Verification by PickPlugins versions before 2.0.49 do not adequately constrain verification attempts or expire generated one-time codes. An unauthenticated attacker may gain access to user accounts, including administrator accounts, when digit-only verification codes are enabled.

mitigation

Update User Verification by PickPlugins to version 2.0.49 or later. Until updated, avoid digit-only verification codes and restrict exposure of the affected login flow.

fixed in 2.0.49

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-12 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-11-12 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4250",
  "cve_id": "CVE-2026-76792",
  "display_id": "CVE-2026-76792",
  "ghsa_id": "GHSA-gmxr-g9qg-qjhg",
  "euvd_id": "EUVD-2026-124289",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OTP verification brute-force flaw in User Verification by PickPlugins",
  "summary": "User Verification by PickPlugins versions before 2.0.49 do not adequately constrain verification attempts or expire generated one-time codes. An unauthenticated attacker may gain access to user accounts, including administrator accounts, when digit-only verification codes are enabled.",
  "mitigation": "Update User Verification by PickPlugins to version 2.0.49 or later. Until updated, avoid digit-only verification codes and restrict exposure of the affected login flow.",
  "vendor": null,
  "product": "User Verification by PickPlugins",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.0.38, < 2.0.49"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.0.49"
      ],
      "package_name": "User Verification by PickPlugins",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.777503333333332,
  "t0_at": "2026-11-12T06:00:10.307000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T06:00:10.307000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T06:00:10.307000+00:00",
      "url": "https://github.com/advisories/GHSA-gmxr-g9qg-qjhg"
    }
  }
}

published 2026-11-12 07:15Z
last change 2026-11-12 07:50Z

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.