# CVE-2026-104648: weMail WordPress plugin API key disclosure to Editor role

Source: https://junglewise.ai/threats/cve-2026-104648-the-wemail-wordpress-plugin-through-2-1-6-does-not-restrict-a  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-104648 · Severity: info · Published 2026-11-03

The weMail WordPress plugin through version 2.1.6 exposes email service API keys on admin screens accessible to users with the Editor role. An attacker with Editor access can obtain the API key and use it to impersonate other users, compromise email delivery, or exploit the email service without needing to log into WordPress.

Technologies: [weMail](https://junglewise.ai/threats/technologies/wemail). Vendors: [weMail](https://junglewise.ai/threats/vendors/wemail).

## Quick answers

**Is CVE-2026-104648 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-104648 being exploited in the wild.

**How severe is CVE-2026-104648?** Informational severity, published 3 November 2026.

**Which products and versions are affected?** weMail through 2.1.6.

**Is there a fix for CVE-2026-104648?** 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-104648 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-104648?** 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 fails to properly restrict access to admin screens containing third-party email-service API keys, allowing Editor-role users (who have default access to certain admin areas) to view and extract reusable credentials. An authenticated attacker with Editor privileges can obtain a site-wide API key and use it for out-of-session authentication to the email service, enabling account impersonation and service disruption.

## Affected products

- weMail weMail through 2.1.6

## Timeline

- 2026-10-31: disclosed
- 2026-11-03: advisory

## References

- [https://wpscan.com/vulnerability/5908e671-7282-48b5-90c9-e85db6b80c52/](https://wpscan.com/vulnerability/5908e671-7282-48b5-90c9-e85db6b80c52/)

## Related threats

- [weMail incorrect authorization in REST API permission checks](https://junglewise.ai/threats/cve-2026-104647-the-wemail-wordpress-plugin-through-2-1-6-does-not-correctly)
- [weMail WordPress plugin Reflected XSS in wemail_preview AJAX action](https://junglewise.ai/threats/cve-2026-8089-wemail-wordpress-plugin-reflected-xss-in-wemail-preview-ajax)