0.0
NA
CVE-2026-104648
weMail <= 2.1.6 - Editor+ API Key Disclosure
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.

INFO

Published Date :

Nov. 3, 2026, 6:17 a.m.

Last Modified :

Nov. 3, 2026, 6:17 a.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-104648 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Restrict API key access and update the plugin to mitigate unauthorized access and impersonation.
  • Update the weMail plugin to the latest version.
  • Restrict access to the API key settings.
  • Change the API key if compromised.
  • Review user roles and permissions.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-104648.

URL Resource
https://wpscan.com/vulnerability/5908e671-7282-48b5-90c9-e85db6b80c52/
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-104648 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-104648 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-104648 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-104648 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Nov. 03, 2026

    Action Type Old Value New Value
    Added 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.
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/104xxx/CVE-2026-104648.json">CVE-2026-104648</a>
    Added Reference https://wpscan.com/vulnerability/5908e671-7282-48b5-90c9-e85db6b80c52/
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.