CVE-2026-114658

validatingZero is analyzing and reversing it now.

GHSA-hgwc-2mf9-5m4j ↗EUVD-2026-107900 ↗

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.
getgrav grav-plugin-login >= 3.6.0, < 3.9.13
fixed in 3.9.13
CWE-269 Improper Privilege Management
ETK-2026-2381Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:composer/getgrav/grav-plugin-login
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Grav Login plugin versions 3.6.0 through 3.9.12 do not properly authorize an invitation-related action. A page author can configure an invitation that permits an unauthenticated person to create an account with superuser access.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade grav-plugin-login to version 3.9.13 or later. Until upgraded, restrict page-authoring access and disable or tightly control invitation forms.

fixed in 3.9.13

check
building now
exploit
not yet
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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 01:43Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-22 01:43Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2381",
  "cve_id": "CVE-2026-114658",
  "display_id": "CVE-2026-114658",
  "ghsa_id": "GHSA-hgwc-2mf9-5m4j",
  "euvd_id": "EUVD-2026-107900",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Authorization bypass in grav-plugin-login invitations",
  "summary": "Grav Login plugin versions 3.6.0 through 3.9.12 do not properly authorize an invitation-related action. A page author can configure an invitation that permits an unauthenticated person to create an account with superuser access.",
  "mitigation": "Upgrade grav-plugin-login to version 3.9.13 or later. Until upgraded, restrict page-authoring access and disable or tightly control invitation forms.",
  "vendor": "getgrav",
  "product": "grav-plugin-login",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.6.0, < 3.9.13"
      ],
      "ecosystem": "composer",
      "fixed_versions": [
        "3.9.13"
      ],
      "package_name": "getgrav/grav-plugin-login",
      "purl": "pkg:composer/getgrav/grav-plugin-login"
    }
  ],
  "cwes": [
    269
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.555713783333335,
  "t0_at": "2026-10-22T01:43:43.437000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T01:43:43.437000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T01:43:43.437000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114658"
    }
  }
}

published 2026-10-22 02:28Z
last change 2026-10-22 04:00Z

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.