The weMail WordPress plugin through 2.1.6 does not restrict a site-wide third-party email-service API key to
Source GCVE Database
Not known to be exploited.
Data as of 3 Nov 2026, 07:43 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| weMail | Affected
| 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.