VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2025-14348Published · Updated

Action summary

Affected: ≤2.0.7Update to 2.0.8 or newer

All remediation steps
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:N Integrity
None
A:N Availability
None
Weakness
CWE-285 Improper Authorization
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce wemail

  1. Affected≤ 2.0.7
  2. Patched in2.0.8

Update to 2.0.8 or newer.

You are affected if you run ≤ 2.0.7. Version 2.0.8 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.0.8, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to shark3y.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce

All 11
More vulnerabilities in weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce
SeverityVulnerabilityCVEPublished
Low2.7Authenticated (Editor+) Information Exposure
<2.1.7Update to 2.1.7
CVE-2026-104648
Low2.7Missing Authorization
<2.1.7Update to 2.1.7
CVE-2026-104647
Medium6.1Reflected Cross-Site Scripting
≤2.1.2Update to 2.1.3
CVE-2026-57322
Medium6.1Reflected Cross-Site Scripting
≤2.1.2Update to 2.1.3
CVE-2026-8089
Medium6.5Missing Authorization to Unauthenticated Form Deletion
≤2.0.7Update to 2.0.8
CVE-2025-14339

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?