CVE-2026-130754

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

GHSA-886c-7cx4-2rw7 ↗EUVD-2026-129154 ↗

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.
laradashboard <= 1.5.4
ETK-2026-4856Zero's internal tracking ID, independent of the CVE number., permanent identifier
57msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h50m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

All LaraDashboard versions are affected by an account-linking flaw in social authentication. An unauthenticated attacker may impersonate another account, including an administrative account, when a configured OAuth/OIDC provider supplies an unverified email address for that user.

mitigation

Disable social OAuth/OIDC login, or restrict it to providers that reliably verify email ownership, until the application validates provider email-verification status before linking accounts. Review existing social-account links for unauthorized associations.

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.
–
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 19:02Z
Δ 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-18 19:02Z
    ghsa: trigger signal, started the run
  2. 2026-11-18 19:02Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4856",
  "cve_id": "CVE-2026-130754",
  "display_id": "CVE-2026-130754",
  "ghsa_id": "GHSA-886c-7cx4-2rw7",
  "euvd_id": "EUVD-2026-129154",
  "status": "published",
  "anchor_state": "anchored",
  "title": "LaraDashboard OAuth email-verification authentication bypass",
  "summary": "All LaraDashboard versions are affected by an account-linking flaw in social authentication. An unauthenticated attacker may impersonate another account, including an administrative account, when a configured OAuth/OIDC provider supplies an unverified email address for that user.",
  "mitigation": "Disable social OAuth/OIDC login, or restrict it to providers that reliably verify email ownership, until the application validates provider email-verification status before linking accounts. Review existing social-account links for unauthorized associations.",
  "vendor": "laradashboard",
  "product": "laradashboard",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.5.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "laradashboard",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.6760784,
  "t0_at": "2026-11-18T19:02:45.620000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T19:02:45.620000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T19:02:45.620000+00:00",
      "url": "https://github.com/advisories/GHSA-886c-7cx4-2rw7"
    }
  }
}

published 2026-11-18 23:25Z
last change 2026-11-18 23:58Z

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.