Quick answers
- Is CVE-2026-104647 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104647 being exploited in the wild.
- How severe is CVE-2026-104647?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- weMail through 2.1.6.
- Is there a fix for CVE-2026-104647?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-104647 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-104647?
- Check whether you run weMail at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The plugin treats any user whose role is in its allowed-roles list (Editor and above by default) as authorized for all REST API actions without proper capability verification, resulting in a horizontal privilege escalation. An authenticated Editor-level user can enumerate all registered users with email addresses and modify the plugin's access-control configuration through REST API calls. The vulnerability exists through version 2.1.6 and requires authentication with at least Editor role.
Affected products
- weMail weMail through 2.1.6
Timeline
- 2026-10-31: disclosed
- 2026-11-03: advisory