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.
Published: 2026-11-03
Score: n/a
EPSS: n/a
KEV: No
Impact: Credential Disclosure and Impersonation
Action: Apply Patch
AI Analysis

Impact

The weMail WordPress plugin version 2.1.6 exposes a third‑party email‑service API key to any user with the Editor role, which is a standard non‑administrative role. This disclosure allows the attacker to obtain a reusable credential that does not require a WordPress session, enabling direct impersonation of other site users and the ability to disconnect the site’s email service. The impact is therefore both credential theft and potential privilege escalation, effectively compromising the integrity and availability of the site’s messaging functionality.

Affected Systems

WeMail WordPress plugin, all installations of version 2.1.6 or earlier from the vendor Unknown:weMail. No specific version range beyond the cutoff is listed, so all releases up to and including 2.1.6 are affected.

Risk and Exploitability

The attack vector is simple: a user with the Editor role can access the default admin screen where the key is displayed. No additional network access or code execution is required. The CVE is not listed in CISA KEV, yet the combination of a widely available role, lack of rate limiting, and complete credential disclosure indicates a high likelihood of exploitation and potentially serious impact if an attacker uses the key to spoof communications or disable email services.

Generated by OpenCVE AI on November 3, 2026 at 07:50 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update to a fixed version of weMail that restricts the API key to administrators.
  • If immediate patching is not possible, remove or disable the third‑party email‑service integration and rotate all existing API keys.
  • Restrict Editor roles from accessing the admin page that displays the API key, or adjust role capabilities to prevent exposure.
  • Monitor site logs for unauthorized access to API key endpoints or sudden changes in email delivery behavior.

Generated by OpenCVE AI on November 3, 2026 at 07:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 03 Nov 2026 08:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-284

Tue, 03 Nov 2026 06:15:00 +0000

Type Values Removed Values 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.
Title weMail <= 2.1.6 - Editor+ API Key Disclosure
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-11-03T06:00:24.220Z

Reserved: 2026-10-02T05:41:48.362Z

Link: CVE-2026-104648

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-03T06:17:37.250

Modified: 2026-11-03T06:17:37.250

Link: CVE-2026-104648

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-03T08:00:15Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-284

    Improper Access Control