WordPress plugin · Updated daily · Source: Wordfence Intelligence

Post SMTP vulnerabilities: affected versions and fixes

Post SMTP has 300,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Post SMTP at a glance

  • 28 publicly disclosed vulnerabilities, 13 of them rated High or Critical. The most recent was disclosed on Oct 5, 2026.
  • Ranked #162 by popularity on WordPress.org (300,000+ active installs).
  • The latest version is 4.0.4 (released Nov 19, 2026). The most recent security fix shipped in 4.0.2.
  • 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 Post SMTP version

Enter the Post SMTP 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 “Post SMTP”, 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.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Post SMTP”.

  2. 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. 3

    Update

    Click “Update now” to move to the latest version (4.0.4). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Post SMTP vulnerabilities (latest 25 of 28)

  • Post SMTP <= 4.0.1 - Unauthenticated Stored DOM-Based Cross-Site Scripting via 'user_email' Parameter (Multisite Registration → Failed Email Log)

    Cross-site scripting (XSS) · CVE-2026-75962

    Affected versions: ≤ 4.0.1

    Fixed in: 4.0.2

    Severity: High 7.2 · Disclosed Oct 5, 2026

  • Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App 4.0.0-beta.1 - Missing Authorization to Authenticated (Subscriber+) Settings Change

    Missing authorization · CVE-2026-81278

    Affected versions: ≥ 4.0.0-beta.1, ≤ 4.0.0-beta.1

    Fixed in: 4.0.1

    Severity: Medium 6.3 · Disclosed Aug 26, 2026

  • Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App <= 3.6.2 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-48838

    Affected versions: ≤ 3.6.2

    Fixed in: 3.6.3

    Severity: High 7.2 · Disclosed May 28, 2026

  • Freemius <= 2.10.1 - Reflected DOM-Based Cross-Site Scripting via url Parameter

    Cross-site scripting (XSS) · CVE-2024-13362

    Affected versions: ≤ 3.0.0

    Fixed in: 3.1.0

    Severity: Medium 6.1 · Disclosed Apr 30, 2026

  • Post SMTP <= 3.8.0 - Unauthenticated Stored Cross-Site Scripting via 'event_type'

    Cross-site scripting (XSS) · CVE-2026-3090

    Affected versions: ≤ 3.8.0

    Fixed in: 3.9.0

    Severity: High 7.2 · Disclosed Mar 17, 2026

  • Post SMTP <= 3.8.0 - Missing Authorization to Authenticated (Subscriber+) Office 365 OAuth Configuration Overwrite

    Missing authorization · CVE-2026-2559

    Affected versions: ≤ 3.8.0

    Fixed in: 3.9.0

    Severity: Medium 5.3 · Disclosed Mar 17, 2026

  • Post SMTP – Complete SMTP Solution with Logs, Alerts, Backup SMTP & Mobile App <= 3.6.1 - Missing Authorization to Authenticated (Subscriber+) OAuth Token Update

    Missing authorization · CVE-2025-12887

    Affected versions: ≤ 3.6.1

    Fixed in: 3.6.2

    Severity: Medium 5.4 · Disclosed Dec 3, 2025

  • Post SMTP – Complete SMTP Solution with Logs, Alerts, Backup SMTP & Mobile App <= 3.6.0 - Missing Authorization to Account Takeover via Unauthenticated Email Log Disclosure

    Missing authorization · CVE-2025-11833

    Affected versions: ≤ 3.6.0

    Fixed in: 3.6.1

    Severity: Critical 9.8 · Disclosed Oct 31, 2025

  • Post SMTP <= 3.4.1 - Missing Authorization to Authenticated (Subscriber+) Limited Plugin Option Update

    Missing authorization · CVE-2025-9219

    Affected versions: ≤ 3.4.1

    Fixed in: 3.4.2

    Severity: Medium 4.3 · Disclosed Sep 2, 2025

  • Post SMTP <= 3.2.0 - Missing Authorization to Authenticated (Subscriber+) Account Takeover via Email Log Exposure

    Missing authorization · CVE-2025-24000

    Affected versions: ≤ 3.2.0

    Fixed in: 3.3.0

    Severity: High 8.8 · Disclosed Jul 21, 2025

  • Post SMTP <= 3.1.2 - Authenticated (Administrator+) SQL Injection via columns Parameter

    SQL injection · CVE-2024-13844

    Affected versions: ≤ 3.1.2

    Fixed in: 3.1.3

    Severity: Medium 4.9 · Disclosed Mar 7, 2025

  • Post SMTP <= 3.0.2 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-0521

    Affected versions: ≤ 3.0.2

    Fixed in: 3.1.0

    Severity: High 7.2 · Disclosed Feb 17, 2025

  • Post SMTP <= 2.9.11 - Missing Authorization via regenerate_qrcode()

    Missing authorization · CVE-2025-22800

    Affected versions: ≤ 2.9.11

    Fixed in: 2.9.12

    Severity: Medium 4.3 · Disclosed Jan 7, 2025

  • Post SMTP <= 2.9.9 - Authenticated (Administrator+) SQL Injection

    SQL injection · CVE-2024-52436

    Affected versions: ≤ 2.9.9

    Fixed in: 2.9.10

    Severity: Medium 4.9 · Disclosed Nov 15, 2024

  • POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress <= 2.9.3 - Authenticated (Administrator+) SQL Injection

    SQL injection · CVE-2024-5207

    Affected versions: ≤ 2.9.3

    Fixed in: 2.9.4

    Severity: High 7.2 · Disclosed May 22, 2024

  • POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress <= 2.8.7 - Authorization Bypass via type connect-app API

    Missing authorization · CVE-2023-6875

    Affected versions: ≤ 2.8.7

    Fixed in: 2.8.8

    Severity: Critical 9.8 · Disclosed Jan 10, 2024

  • POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress <= 2.8.7 - Unauthenticated Stored Cross-Site Scripting via device

    Cross-site scripting (XSS) · CVE-2023-7027

    Affected versions: ≤ 2.8.7

    Fixed in: 2.8.8

    Severity: High 7.2 · Disclosed Jan 2, 2024

  • POST SMTP Mailer <= 2.8.6 - Reflected Cross-Site Scripting via msg

    Cross-site scripting (XSS) · CVE-2023-6629

    Affected versions: ≤ 2.8.6

    Fixed in: 2.8.7

    Severity: Medium 6.1 · Disclosed Jan 2, 2024

  • POST SMTP Mailer – Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress <= 2.8.6 - Authenticated (Administrator+) SQL Injection

    SQL injection · CVE-2023-6620

    Affected versions: ≤ 2.8.6

    Fixed in: 2.8.7

    Severity: High 7.2 · Disclosed Dec 21, 2023

  • POST SMTP Mailer <= 2.7.0 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-5958

    Affected versions: ≤ 2.7.0

    Fixed in: 2.7.1

    Severity: High 7.2 · Disclosed Nov 6, 2023

  • Post SMTP <= 2.6.0 - Authenticated (Administrator+) SQL Injection

    SQL injection

    Affected versions: < 2.6.1

    Fixed in: 2.6.1

    Severity: High 7.2 · Disclosed Oct 3, 2023

  • Freemius SDK <= 2.5.9 - Reflected Cross-Site Scripting via fs_request_get

    Cross-site scripting (XSS) · CVE-2023-33999

    Affected versions: ≥ 2.1.2-beta.1, ≤ 2.5.7

    Fixed in: 2.5.9-beta.1

    Severity: Medium 6.1 · Disclosed Jul 18, 2023

  • Post SMTP <= 2.5.7 - Unauthenticated Stored Cross-Site Scripting via Email

    Cross-site scripting (XSS) · CVE-2023-3082

    Affected versions: ≤ 2.5.7

    Fixed in: 2.5.8

    Severity: High 7.2 · Disclosed Jul 11, 2023

  • POST SMTP Mailer <= 2.5.6 - Cross-Site Request Forgery to Account Compromise

    Cross-site request forgery (CSRF) · CVE-2023-3179

    Affected versions: ≤ 2.5.6

    Fixed in: 2.5.7

    Severity: Medium 6.5 · Disclosed Jun 26, 2023

  • POST SMTP Mailer <= 2.5.6 - Cross-Site Request Forgery to Arbitrary Log Deletion

    Cross-site request forgery (CSRF) · CVE-2023-3178

    Affected versions: ≤ 2.5.6

    Fixed in: 2.5.7

    Severity: Medium 4.3 · Disclosed Jun 26, 2023

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 5, 2026.

Most common weaknesses in Post SMTP

Cross-site scripting (XSS)

11 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.

Missing authorization

8 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.

SQL injection

5 issues

Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.

Frequently asked questions

Is Post SMTP safe to use?

Post SMTP is a well-known plugin with 300,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 (4.0.4) and turn on automatic updates.

How do I find which version of Post SMTP 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.

← All plugin vulnerabilitiesPost SMTP on WordPress.org