CVE-2026-84740

validatedZero produced an exploit or a check.

GHSA-4c37-j68q-cmxj ↗EUVD-2026-91210 ↗

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).+0mkevAttacks confirmed in the real world.+20d
StellarWP The Events Calendar >= 6.12.0, < 6.17.5.1
fixed in 6.17.5.1
ETK-2026-2492Zero's internal tracking ID, independent of the CVE number., permanent identifier
+21dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−20dpublic poctrigger signal +0dcheck available+0.8dkev+1.0dagent stopped
−15d
−10d
−5d

description

The Events Calendar versions before 6.17.5.1 are affected by inadequate input handling in an unauthenticated AJAX action. A remote unauthenticated attacker can cause execution of shortcodes registered on the affected WordPress site. Exploitation requires the vulnerable plugin version and reachable unauthenticated AJAX functionality.

mitigation

Update The Events Calendar to version 6.17.5.1 or later. Restrict public access to the affected WordPress site until the update is installed if immediate patching is not possible.

fixed in 6.17.5.1

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-10-02 06:56Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+0m
Δ to kevAttacks confirmed in the real world.
+20d

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-10-02 06:56Z
  2. 2026-10-22
    vulncheck_kev: trigger signal, started the run
  3. 2026-10-22 00:00Z
  4. 2026-10-22 20:22Z
  5. 2026-10-22 20:34Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2492",
  "cve_id": "CVE-2026-84740",
  "display_id": "CVE-2026-84740",
  "ghsa_id": "GHSA-4c37-j68q-cmxj",
  "euvd_id": "EUVD-2026-91210",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated shortcode injection in The Events Calendar",
  "summary": "The Events Calendar versions before 6.17.5.1 are affected by inadequate input handling in an unauthenticated AJAX action. A remote unauthenticated attacker can cause execution of shortcodes registered on the affected WordPress site. Exploitation requires the vulnerable plugin version and reachable unauthenticated AJAX functionality.",
  "mitigation": "Update The Events Calendar to version 6.17.5.1 or later. Restrict public access to the affected WordPress site until the update is installed if immediate patching is not possible.",
  "vendor": "StellarWP",
  "product": "The Events Calendar",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.12.0, < 6.17.5.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.17.5.1"
      ],
      "package_name": "The Events Calendar",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 6.5,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.0186631,
  "t0_at": "2026-10-02T06:56:50.295000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-22T20:22:30.934613+00:00",
      "days": 20.559498143668982,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T06:56:50.295000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-22T00:00:00+00:00",
      "days": 20,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T06:56:50.295000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-84740"
    },
    "public_poc": {
      "at": "2026-10-02T06:56:50.295000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T06:56:50.295000+00:00",
      "url": "https://wpscan.com/vulnerability/3381a51e-beaa-4420-a33b-6a68612a2e8a/"
    },
    "trigger_signal": {
      "at": "2026-10-22T00:00:00+00:00",
      "days": 19.710528993055554,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T06:56:50.295000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-84740"
    }
  }
}

published 2026-10-22 20:22Z
last change 2026-10-22 21:37Z

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.