CVE-2026-10818

validatedZero produced an exploit or a check.

GHSA-g685-9q2w-88f4 ↗EUVD-2026-48766 ↗

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).+81dkevAttacks confirmed in the real world.+80d
wpforms <= 1.10.1.1
ETK-2026-1557Zero's internal tracking ID, independent of the CVE number., permanent identifier
+81dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−80dtrigger signal +0dkev+1.0dcheck available+1.4dpublic pocagent stopped
−60d
−40d
−20d

description

WPForms Pro versions through 1.10.1.1 are affected by an arbitrary file upload vulnerability. An unauthenticated attacker may upload files that can be executable, potentially leading to remote code execution; exploitation requires the vulnerable upload functionality to be reachable.

mitigation

Upgrade WPForms Pro when a vendor-fixed release is available; no fixed version is recorded in the advisory. Until then, reduce exposure by disabling or restricting public access to the affected upload functionality.

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.
2.5%84th percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-07-25 06:50Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+81d
Δ to kevAttacks confirmed in the real world.
+80d

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-07-25 06:50Z
  2. 2026-10-13
    vulncheck_kev: trigger signal, started the run
  3. 2026-10-13 00:00Z
  4. 2026-10-14 09:39Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1557",
  "cve_id": "CVE-2026-10818",
  "display_id": "CVE-2026-10818",
  "ghsa_id": "GHSA-g685-9q2w-88f4",
  "euvd_id": "EUVD-2026-48766",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated arbitrary file upload in WPForms Pro",
  "summary": "WPForms Pro versions through 1.10.1.1 are affected by an arbitrary file upload vulnerability. An unauthenticated attacker may upload files that can be executable, potentially leading to remote code execution; exploitation requires the vulnerable upload functionality to be reachable.",
  "mitigation": "Upgrade WPForms Pro when a vendor-fixed release is available; no fixed version is recorded in the advisory. Until then, reduce exposure by disabling or restricting public access to the affected upload functionality.",
  "vendor": "wpforms",
  "product": "wpforms",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.10.1.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WPForms Pro",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0248,
  "epss_percentile": 0.8437,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.019049466666666667,
  "t0_at": "2026-07-25T06:50:06.104000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-14T09:39:22.809782+00:00",
      "days": 81.11755446506945,
      "is_lower_bound": false,
      "measured_at": "2026-07-25T06:50:06.104000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-13T00:00:00+00:00",
      "days": 80,
      "is_lower_bound": false,
      "measured_at": "2026-07-25T06:50:06.104000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-10818"
    },
    "public_poc": {
      "at": "2026-10-14T09:39:22.836479+00:00",
      "days": 81.1175547740625,
      "is_lower_bound": false,
      "measured_at": "2026-07-25T06:50:06.104000+00:00",
      "url": "https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-10818.yaml"
    },
    "trigger_signal": {
      "at": "2026-10-13T00:00:00+00:00",
      "days": 79.71520712962963,
      "is_lower_bound": false,
      "measured_at": "2026-07-25T06:50:06.104000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-10818"
    }
  }
}

published 2026-10-14 09:39Z
last change 2026-10-21 06:02Z

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.