Skip to main content
CVE-2026-104648VulnerabilityPublished

The weMail WordPress plugin through 2.1.6 does not restrict a site-wide third-party email-service API key to

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-104648· High

Not known to be exploited.

Data as of 3 Nov 2026, 07:43 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
weMailAffected
  • <=2.1.6
Fixed in–

AI-suggested

Until a fix is available, restrict Editor role access to the affected admin screens or remove the plugin if possible.

Description

The weMail WordPress plugin versions through 2.1.6 expose a site-wide third-party email-service API key to users with the Editor role by displaying it on an admin screen accessible to them. This exposure allows Editors to obtain a reusable credential that can be used without a WordPress session to impersonate other users and disrupt the site's email-service connection.

References

Community reviews

Loading reviews…