Security readout for executives and security teams
Plain-English summary
CVE-2026-2559 affects the Post SMTP WordPress plugin through version 3.8.0. A low-privileged logged-in user could overwrite Office 365 OAuth mail settings used during Microsoft365 SMTP setup in the Pro option. This could mislead an administrator into connecting mail delivery to an attacker-controlled Microsoft/Azure application.
Executive priority
Treat as a medium-priority WordPress plugin issue. It is not reported as actively exploited, but it can undermine email configuration integrity on sites with low-privileged users. Prioritize patching public or multi-user WordPress sites and verify Microsoft365 mail settings before administrator setup actions.
Technical view
The issue is missing authorization in handle_office365_oauth_redirect(), hooked to admin_init without current_user_can() or nonce verification. Authenticated Subscriber-level users can modify stored Office 365 OAuth configuration values, including access token, refresh token, and user email. CVSS is 5.3, with high integrity impact and high attack complexity.
Likely exposure
Exposure is limited to WordPress sites running Post SMTP up to and including 3.8.0, especially sites with untrusted Subscriber-level accounts. The affected configuration path relates to Microsoft365 SMTP wizard setup in the plugin’s Pro option, reducing broad impact but not eliminating risk.
Exploitation context
The sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires an authenticated WordPress account at Subscriber level or higher. The attacker’s practical goal is configuration tampering, potentially influencing a later administrator setup flow.
Researcher notes
The key weakness is CWE-862: missing authorization. Sources identify admin_init exposure without capability or nonce checks. The business impact depends on the Pro Microsoft365 setup workflow and whether an attacker can obtain any authenticated account. Avoid assuming mailbox compromise without confirming subsequent administrator interaction.
Mitigation direction
- Upgrade Post SMTP to a vendor-fixed version newer than 3.8.0 when available.
- Review vendor and Wordfence guidance for the exact fixed release.
- Limit or remove untrusted Subscriber-level accounts until remediated.
- Recheck Microsoft365 SMTP OAuth settings before completing or re-running setup.
- Audit recent changes to Post SMTP Office 365 OAuth configuration.
Validation and detection
- Inventory WordPress sites using the Post SMTP plugin.
- Identify plugin versions up to and including 3.8.0.
- Confirm whether Microsoft365 SMTP or the Pro setup wizard is used.
- Review WordPress users with Subscriber-level or higher access.
- Check plugin changelog or Trac changeset for authorization and nonce fixes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-2559 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N1.63.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/323436b5-fbfe-4923-8b08-93c1fcabc016?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/post-smtp/trunk/Postman/Wizard/NewWizard.php#L2109CVE reference
- https://plugins.trac.wordpress.org/changeset/3484515/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.