CVE-2026-2559

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

2026-03-17 00:00
Michael Iden (Mickhat)

At a glance

CVE-2026-2559 is a medium-severity Missing Authorization vulnerability in the Post SMTP WordPress plugin, affecting versions <= 3.8.0. It carries a CVSS score of 5.3 (reachable over the network; high integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.9.0; sites on affected versions should update now. Disclosed March 2026, reported by Michael Iden (Mickhat).

Vulnerability Overview

The Post SMTP plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `handle_office365_oauth_redirect()` function in all versions up to, and including, 3.8.0. This is due to the function being hooked to `admin_init` without any `current_user_can()` check or nonce verification. This makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the site's Office 365 OAuth mail configuration (access token, refresh token, and user email) via a crafted URL. The configuration option is used during wizard setup of Microsoft365 SMTP, only available in the Pro option of the plugin. This could cause an Administrator to believe an attacker-controlled Azure app is their own, and lead them to connect the plugin to the attacker's account during configuration after upgrading to Pro.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

Post SMTP <= 3.8.0 carries this weakness at handle_office365_oauth_redirect(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Post SMTP the fix is 3.9.0: builds <= 3.8.0 are affected, anything from 3.9.0 onward is not.

Remediation

Update to version 3.9.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Post SMTP 3.9.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C