CVE-2025-14348 MEDIUM

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

Vendor Wedevs
Product weMail: Email Marketing, Email Automation, Newsletters, Subscribers & Email Optins for WooCommerce
Weakness CWE-285
Published January 20, 2026
Last update April 8, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

weMail versions up to 2.0.7 contain an improper access control vulnerability that allows unauthenticated attackers to read sensitive information over the network. The vulnerability requires no user interaction and can be exploited remotely. Site administrators should update to a version newer than 2.0.7 to remediate this issue.

What an attacker can do

03Attacker Capabilities

Read sensitive information from the plugin without authentication.

Potential impact on your site

04Site Impact

Sensitive data may be exposed to unauthenticated visitors without your knowledge.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

January 20, 2026 CVE published
April 8, 2026 Record updated