CVE-2026-104648

validatedZero produced an exploit or a check.

GHSA-933g-gq9w-6rm8 ↗EUVD-2026-115683 ↗

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.
weMail <= 2.1.6
ETK-2026-3346Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1h38mTTV
18mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+98magent stopped
0
+30min
+60min
+90min

description

weMail versions through 2.1.6 expose a site-wide email-service API key through an interface reachable by default to users with the WordPress Editor role. An attacker who has an Editor account can obtain the credential and use it outside the site to impersonate users or disrupt the email-service connection.

mitigation

Remove or limit Editor accounts until the plugin is updated, and restrict access to the affected weMail administration interface. Upgrade to a weMail release newer than 2.1.6 after confirming it corrects the authorization check.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 06:00Z
Δ 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-11-03 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-11-03 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3346",
  "cve_id": "CVE-2026-104648",
  "display_id": "CVE-2026-104648",
  "ghsa_id": "GHSA-933g-gq9w-6rm8",
  "euvd_id": "EUVD-2026-115683",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Editor-accessible API key disclosure in weMail",
  "summary": "weMail versions through 2.1.6 expose a site-wide email-service API key through an interface reachable by default to users with the WordPress Editor role. An attacker who has an Editor account can obtain the credential and use it outside the site to impersonate users or disrupt the email-service connection.",
  "mitigation": "Remove or limit Editor accounts until the plugin is updated, and restrict access to the affected weMail administration interface. Upgrade to a weMail release newer than 2.1.6 after confirming it corrects the authorization check.",
  "vendor": null,
  "product": "weMail",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.1.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "weMail",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 17.8940986,
  "t0_at": "2026-11-03T06:00:24.220000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-03T07:38:01.165604+00:00",
      "days": 0.06778872226851852,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T06:00:24.220000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-03T06:00:24.220000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T06:00:24.220000+00:00",
      "url": "https://github.com/advisories/GHSA-933g-gq9w-6rm8"
    }
  }
}

published 2026-11-03 07:20Z
last change 2026-11-03 08:30Z

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.