CVE-2024-58390

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

GHSA-g6cq-m3m2-c4h3 ↗EUVD-2024-55785 ↗

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.
frappe < 14.81.4; >= 15.0.0, < 15.41.0
fixed in 14.81.4, 15.41.0
ETK-2026-1446Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 04h 01msince last run
52mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h24m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Frappe releases before 14.81.4 and 15.41.0 on the 15.x line have an authorization-management flaw affecting a document action. An authenticated user assigned the Website User role may be able to gain System Manager administrative privileges.

mitigation

Upgrade Frappe 14.x to 14.81.4 or later, or upgrade 15.x to 15.41.0 or later. Until upgraded, restrict or review Website User accounts and their access to document actions.

fixed in 14.81.4, 15.41.0

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.27%17th percentile
agent run time
52m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 22:21Z
Δ 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-12 22:21Z
    ghsa: trigger signal, started the run
  2. 2026-10-12 22:21Z

this entry in the feed

GET /api/v1/feed/CVE-2024-58390

{
  "etk_id": "ETK-2026-1446",
  "cve_id": "CVE-2024-58390",
  "display_id": "CVE-2024-58390",
  "ghsa_id": "GHSA-g6cq-m3m2-c4h3",
  "euvd_id": "EUVD-2024-55785",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Document-action privilege escalation in Frappe",
  "summary": "Frappe releases before 14.81.4 and 15.41.0 on the 15.x line have an authorization-management flaw affecting a document action. An authenticated user assigned the Website User role may be able to gain System Manager administrative privileges.",
  "mitigation": "Upgrade Frappe 14.x to 14.81.4 or later, or upgrade 15.x to 15.41.0 or later. Until upgraded, restrict or review Website User accounts and their access to document actions.",
  "vendor": "frappe",
  "product": "frappe",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 14.81.4",
        ">= 15.0.0, < 15.41.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "14.81.4",
        "15.41.0"
      ],
      "package_name": "frappe",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0027,
  "epss_percentile": 0.1773,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 51.54459036666667,
  "t0_at": "2026-10-12T22:21:44.339000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T22:21:44.339000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T22:21:44.339000+00:00",
      "url": "https://github.com/advisories/GHSA-g6cq-m3m2-c4h3"
    }
  }
}

published 2026-10-13 00:53Z
last change 2026-10-21 04:45Z

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.