CVE-2025-14348

weMail <= 2.0.7 - Insufficient Authorization via x-wemail-user Header to Sensitive Information Disclosure

2026-01-19 15:57
shark3y

Strategic Overview

Status
Patched in 2.0.8
Affected Version
<= 2.0.7
CVSS
5.3Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2025-14348
View all weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce vulnerabilities

At a glance

CVE-2025-14348 is a medium-severity Improper Authorization vulnerability in the weMail WordPress plugin, affecting versions <= 2.0.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.8; sites on affected versions should update now. Disclosed January 2026, reported by shark3y.

Vulnerability Overview

The weMail - Email Marketing, Lead Generation, Optin Forms, Email Newsletters, A/B Testing, and Automation plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.0.7. This is due to the plugin's REST API trusting the `x-wemail-user` HTTP header to identify users without verifying the request originates from an authenticated WordPress session. This makes it possible for unauthenticated attackers who know or can guess an admin email (easily enumerable via `/wp-json/wp/v2/users`) to impersonate that user and access the CSV subscriber endpoints, potentially exfiltrating subscriber PII (emails, names, phone numbers) from imported CSV files.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-285: Improper Authorization

Reaching this weakness in weMail <= 2.0.7 takes a caller who can reach the endpoint. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For weMail the fix is 2.0.8: builds <= 2.0.7 are affected, anything from 2.0.8 onward is not.

Remediation

Update to version 2.0.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: weMail 2.0.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C