Plugins · mailerpress · data as of 2026-11-04
Is MailerPress safe? Known vulnerabilities and latest version
- Latest version
- 2.2
- Last updated
- 2026-10-26
- Active installs
- 1,000+
- Known issues on record
- 5
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 8.2+
Write, send and track newsletters from WordPress. Block-based email editor, unlimited contacts and lists, sending through your host or SMTP. — by MailerPress Team
What to do
- Update to the latest version (2.2). Anything older than 2.0.5 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get mailerpress --field=version shows what you run; wp plugin update mailerpress updates it.
Check your version
Known vulnerabilities
5 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 5.3 CVE-2026-18436 · published 2026-07-31
Missing authorization check in MailerPress (1.5.0 and older)
- Affected
- 1.5.0 and older
- Fixed in
- 1.5.1 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The MailPress plugin for WordPress is vulnerable to unauthorized access in versions up to, and including, 1.5.0 via the campaign revision-restore REST endpoint (POST /wp-json/mailpress/v1/campaign/<id>/restore-revision/<revision_id>). The route in the vulnerable range was registered without a permissionCallback, allowing the restoreRevision() handler to run for unauthenticated requests and overwrite a campaign's content_html with any prior revision. This makes it possible for unauthenticated attackers to modify campaign content by restoring an arbitrary revision.
medium 5.3 CVE-2026-18437 · published 2026-07-31
Missing authorization check in MailerPress (1.5.0 and older)
- Affected
- 1.5.0 and older
- Fixed in
- 1.5.1 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The MailerPress – Newsletter, email marketing & AI automation plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the `mailerpress/v1/contact` endpoint in all versions up to, and including, 1.5.0. This makes it possible for unauthenticated attackers to update contact details.
high 8.8 CVE-2026-57410 · published 2026-07-13
Privilege escalation in MailerPress (2.0.2 and older)
- Affected
- 2.0.2 and older
- Fixed in
- 2.0.3
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Incorrect Privilege Assignment vulnerability in MailerPress Team MailerPress mailerpress allows Privilege Escalation.This issue affects MailerPress: from n/a through <= 2.0.2.
medium 6.4 CVE-2026-8599 · published 2026-06-09
Stored cross-site scripting (XSS) in MailerPress (2.0.4 and older)
- Affected
- 2.0.4 and older
- Fixed in
- 2.0.5 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The MailerPress – Email Marketing, Newsletter, Email Automation & WooCommerce Emails plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Campaign HTML Content Field in all versions up to, and including, 2.0.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The public-facing campaign preview endpoint (/mp-email/{id}-slug/) is not affected by this vulnerability, as it applies a Content-Security-Policy header blocking all inline scripts; exploitation is limited to the admin dashboard preview.
medium 6.4 CVE-2026-32353 · published 2026-03-13
Server-side request forgery (SSRF) in MailerPress (1.4.2 and older)
- Affected
- 1.4.2 and older
- Fixed in
- 1.5.0
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Server-Side Request Forgery (SSRF) vulnerability in MailerPress Team MailerPress mailerpress allows Server Side Request Forgery.This issue affects MailerPress: from n/a through <= 1.4.2.
Recent activity
- 2026-10-26 — latest release on wordpress.org (2.2).
- 2026-07-31 — Missing authorization check disclosed (CVE-2026-18436), fixed in 1.5.1.
- 2026-07-31 — Missing authorization check disclosed (CVE-2026-18437), fixed in 1.5.1.
- 2026-07-13 — Privilege escalation disclosed (CVE-2026-57410), fixed in 2.0.3.
Get an email when MailerPress has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for MailerPress (mailerpress) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Missing authorization (2) · Privilege escalation (1) · Cross-site scripting (XSS) (1) · Server-side request forgery (SSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/mailerpress (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/mailerpress"><img src="https://laskyr.com/plugins/mailerpress/badge.svg" alt="MailerPress vulnerability status"></a>