CVE-2026-115483

validatedZero produced an exploit or a check.

GHSA-65x7-x9p9-rjjj ↗EUVD-2026-122685 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
wpeverest Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI <= 3.6.3
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-4089Zero's internal tracking ID, independent of the CVE number., permanent identifier
+9mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+9magent stopped
0
+2min
+4min
+6min
+8min
+10min

description

Everest Forms for WordPress through 3.6.3 can expose files readable by the web server when affected Pro add-on features are enabled. An unauthenticated attacker may obtain sensitive file contents if a form uses email attachments, includes a signature-related field, and can send the notification to an attacker-controlled address.

mitigation

Disable notification file attachments and remove or disable signature-related fields on exposed forms until a vendor update is available. Restrict notification recipients to trusted, fixed addresses and review existing form notification settings.

check
available
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.
deterministic
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
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 19:31Z
Δ 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

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-11-10 19:31Z
    cve_org: trigger signal, started the run
  2. 2026-11-10 19:40Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4089",
  "cve_id": "CVE-2026-115483",
  "display_id": "CVE-2026-115483",
  "ghsa_id": "GHSA-65x7-x9p9-rjjj",
  "euvd_id": "EUVD-2026-122685",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file read in Everest Forms for WordPress",
  "summary": "Everest Forms for WordPress through 3.6.3 can expose files readable by the web server when affected Pro add-on features are enabled. An unauthenticated attacker may obtain sensitive file contents if a form uses email attachments, includes a signature-related field, and can send the notification to an attacker-controlled address.",
  "mitigation": "Disable notification file attachments and remove or disable signature-related fields on exposed forms until a vendor update is available. Restrict notification recipients to trusted, fixed addresses and review existing form notification settings.",
  "vendor": "wpeverest",
  "product": "Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.6.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI",
      "purl": null
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.010773116666666667,
  "t0_at": "2026-11-10T19:31:31.738000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-10T19:40:30.931833+00:00",
      "days": 0.0062406693634259255,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T19:31:31.738000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-10T19:31:31.738000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T19:31:31.738000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-115483"
    }
  }
}

published 2026-11-10 19:40Z
last change 2026-11-11 06:19Z

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.