weMail at a glance
- 11 publicly disclosed vulnerabilities. The most recent was disclosed on Nov 3, 2026.
- Ranked #2154 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 2.1.9 (released Nov 11, 2026). The most recent security fix shipped in 2.1.7.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your weMail version
Enter the weMail version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “weMail”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “weMail”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2.1.9). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known weMail vulnerabilities
weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce < 2.1.7 - Missing Authorization
Missing authorization · CVE-2026-104647
Affected versions: < 2.1.7
Fixed in: 2.1.7
Severity: Low 2.7 · Disclosed Nov 3, 2026
weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce < 2.1.7 - Authenticated (Editor+) Information Exposure
Information disclosure · CVE-2026-104648
Affected versions: < 2.1.7
Fixed in: 2.1.7
Severity: Low 2.7 · Disclosed Nov 3, 2026
weMail – Email Marketing, Newsletter Builder & Email Automations for WooCommerce <= 2.1.2 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-57322
Affected versions: ≤ 2.1.2
Fixed in: 2.1.3
Severity: Medium 6.1 · Disclosed Jun 26, 2026
weMail <= 2.1.2 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-8089
Affected versions: ≤ 2.1.2
Fixed in: 2.1.3
Severity: Medium 6.1 · Disclosed May 27, 2026
weMail <= 2.0.7 - Missing Authorization to Unauthenticated Form Deletion
Missing authorization · CVE-2025-14339
Affected versions: ≤ 2.0.7
Fixed in: 2.0.8
Severity: Medium 6.5 · Disclosed Feb 20, 2026
weMail <= 2.0.7 - Insufficient Authorization via x-wemail-user Header to Sensitive Information Disclosure
Missing authorization · CVE-2025-14348
Affected versions: ≤ 2.0.7
Fixed in: 2.0.8
Severity: Medium 5.3 · Disclosed Jan 19, 2026
weMail <= 1.14.13 - Unauthenticated Sensitive Information Exposure
Information disclosure · CVE-2025-47540
Affected versions: ≤ 1.14.13
Fixed in: 1.14.14
Severity: Medium 5.3 · Disclosed May 7, 2025
weMail <= 1.14.5 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-43238
Affected versions: ≤ 1.14.5
Fixed in: 1.14.6
Severity: Medium 6.1 · Disclosed Aug 12, 2024
weMail <= 1.14.2 - Missing Authorization to Notice Dismissal
Missing authorization · CVE-2024-34822
Affected versions: ≤ 1.14.2
Fixed in: 1.14.3
Severity: Medium 5.3 · Disclosed May 15, 2024
Appsero <= 1.2.1 - Missing Authorization
Missing authorization
Affected versions: ≤ 1.14.1
Fixed in: 1.14.2
Severity: Medium 4.3 · Disclosed Dec 16, 2022
Appsero <= 1.2.0 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2022-47150
Affected versions: ≤ 1.14.1
Fixed in: 1.14.2
Severity: Medium 4.3 · Disclosed Dec 14, 2022
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce < 2.1.7 - Missing AuthorizationMissing authorization · CVE-2026-104647 | < 2.1.7 | 2.1.7 | Low 2.7 | Nov 3, 2026 |
| weMail – Email Marketing, Newsletters Builder & Email Automations for WooCommerce < 2.1.7 - Authenticated (Editor+) Information ExposureInformation disclosure · CVE-2026-104648 | < 2.1.7 | 2.1.7 | Low 2.7 | Nov 3, 2026 |
| weMail – Email Marketing, Newsletter Builder & Email Automations for WooCommerce <= 2.1.2 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-57322 | ≤ 2.1.2 | 2.1.3 | Medium 6.1 | Jun 26, 2026 |
| weMail <= 2.1.2 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-8089 | ≤ 2.1.2 | 2.1.3 | Medium 6.1 | May 27, 2026 |
| weMail <= 2.0.7 - Missing Authorization to Unauthenticated Form DeletionMissing authorization · CVE-2025-14339 | ≤ 2.0.7 | 2.0.8 | Medium 6.5 | Feb 20, 2026 |
| weMail <= 2.0.7 - Insufficient Authorization via x-wemail-user Header to Sensitive Information DisclosureMissing authorization · CVE-2025-14348 | ≤ 2.0.7 | 2.0.8 | Medium 5.3 | Jan 19, 2026 |
| weMail <= 1.14.13 - Unauthenticated Sensitive Information ExposureInformation disclosure · CVE-2025-47540 | ≤ 1.14.13 | 1.14.14 | Medium 5.3 | May 7, 2025 |
| weMail <= 1.14.5 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-43238 | ≤ 1.14.5 | 1.14.6 | Medium 6.1 | Aug 12, 2024 |
| weMail <= 1.14.2 - Missing Authorization to Notice DismissalMissing authorization · CVE-2024-34822 | ≤ 1.14.2 | 1.14.3 | Medium 5.3 | May 15, 2024 |
| Appsero <= 1.2.1 - Missing AuthorizationMissing authorization | ≤ 1.14.1 | 1.14.2 | Medium 4.3 | Dec 16, 2022 |
| Appsero <= 1.2.0 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2022-47150 | ≤ 1.14.1 | 1.14.2 | Medium 4.3 | Dec 14, 2022 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 3, 2026.
Most common weaknesses in weMail
Missing authorization
5 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site scripting (XSS)
3 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Information disclosure
2 issues
Data that should stay private, such as user details or configuration values, can be read from outside.
Frequently asked questions
Is weMail safe to use?
weMail is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.1.9) and turn on automatic updates.
How do I find which version of weMail my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.