The weMail WordPress plugin through 2.1.6 does not correctly verify user capabilities in its REST API permission
Source GCVE Database
Not known to be exploited.
Data as of 3 Nov 2026, 07:30 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 user roles to trusted individuals and review role assignments carefully to limit exposure.
Description
The weMail WordPress plugin through version 2.1.6 has a vulnerability in its REST API permission checks that allows users with roles in the plugin's allowed-roles list (Editor and above by default) to perform administrator-level actions. This includes enumerating all registered users with their email addresses and modifying the plugin's access-control configuration.