CVE-2026-64947

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

GHSA-cqqp-fqm5-2w6f ↗EUVD-2026-90596 ↗

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.
Pandora FMS 777
CWE-434 Unrestricted Upload of File with Dangerous Type
ETK-2026-239, permanent identifier
20d 01h 51msince last run
42mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h20m
0
+2h
+6h
+8h
+10h
+12h

description

Pandora FMS releases from 777 onward are affected in the Plugin File Manager. An attacker who can combine the CSRF-bypass and unrestricted-upload flaws may trigger execution of PHP code; the advisory does not specify further access prerequisites.

mitigation

Disable the Plugin File Manager where it is not needed, or restrict its access to trusted administrators and reduce its network exposure. Monitor for vendor remediation because no fixed version is recorded.

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.25%15th percentile
agent run time
42m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 09:27Z
Δ 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-01 09:27Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-239",
  "cve_id": "CVE-2026-64947",
  "display_id": "CVE-2026-64947",
  "ghsa_id": "GHSA-cqqp-fqm5-2w6f",
  "euvd_id": "EUVD-2026-90596",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CSRF bypass and unrestricted upload in Pandora FMS Plugin File Manager",
  "summary": "Pandora FMS releases from 777 onward are affected in the Plugin File Manager. An attacker who can combine the CSRF-bypass and unrestricted-upload flaws may trigger execution of PHP code; the advisory does not specify further access prerequisites.",
  "mitigation": "Disable the Plugin File Manager where it is not needed, or restrict its access to trusted administrators and reduce its network exposure. Monitor for vendor remediation because no fixed version is recorded.",
  "vendor": "Pandora FMS",
  "product": "Pandora FMS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "777"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Pandora FMS",
      "purl": null
    }
  ],
  "cwes": [
    434
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/S:N/AU:Y/R:I/V:C/RE:H/U:Red",
  "epss_score": 0.0025,
  "epss_percentile": 0.1543,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 41.64123481666667,
  "t0_at": "2026-10-01T09:27:46.696000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T09:27:46.696000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T09:27:46.696000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64947"
    }
  }
}

published 2026-10-01 13:06Z
last change 2026-10-21 15:29Z

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.