HomeWordPress vulnerabilitiesweMail
weMail vulnerabilities
weMail has 2 known vulnerabilities in this database. The most recent published record is dated 21 Feb 2026.
- Known vulnerabilities
- 2
- Active installs
- 10,000+
- Latest version
- 2.1.6
- Last updated
- 1 Oct 2026
- Most recent
- 21 Feb 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2025-14339 | Medium 6.5 | Up to 2.0.7 | Fixed in a later version (latest 2.1.6) | 21 Feb 2026 |
| Broken access control CVE-2025-14348 | Medium 5.3 | Up to 2.0.7 | Fixed in a later version (latest 2.1.6) | 20 Jan 2026 |
Read the published descriptions
- CVE-2025-14339, 21 Feb 2026
- The weMail - Email Marketing, Lead Generation, Optin Forms, Email Newsletters, A/B Testing, and Automation plugin for WordPress is vulnerable to unauthorized form deletion in all versions up to, and including, 2.0.7. This is due to the `Forms::permission()` callback only validating the `X-WP-Nonce` header without checking user capabilities. Since the REST nonce is exposed to unauthenticated visitors via the `weMail` JavaScript object on pages with weMail forms, any unauthenticated user can permanently delete all weMail forms by extracting the nonce from the page source and sending a DELETE request to the forms endpoint. CVE record
- CVE-2025-14348, 20 Jan 2026
- 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. CVE record
What to do if you run weMail
If you run weMail, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new weMail vulnerabilities
Free. We email you when a new vulnerability is published for weMail, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.