CVE Tools

CVE-2025-11833

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

Exploitation likely. EPSS gives it a 60% chance of exploitation in the next 30 days. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether your WordPress site uses “post smtp” (Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App) and note the installed version.
  2. If the version is 3.6.0 or earlier, treat the site as exposed because attackers can read email logs without authentication.
  3. Upgrade Post SMTP to a version that includes the authorization fix (the vendor fix is referenced in the PostmanEmailLogs.php change around the 3386160 changeset; verify your upgrade includes that fix).
  4. After upgrading, review Post SMTP email log storage and access controls, and rotate any credentials that might have been reset using exposed links.

What it is

From the CVE record

The Post SMTP – Complete SMTP Solution with Logs, Alerts, Backup SMTP & Mobile App plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the __construct function in all versions up to, and including, 3.6.0. This makes it possible for unauthenticated attackers to read arbitrary logged emails sent through the Post SMTP plugin, including password reset emails containing password reset links, which can lead to account takeover.

In plain language

Written by AI from the record

Post SMTP (WordPress) lets outsiders read your email logs without logging in (including password reset emails) if you’re on 3.6.0 or older—this is a serious account-hijacking risk for a typical small business.

Unauthenticated attacker can bypass a missing authorization (missing capability check on the plugin __construct) to disclose Post SMTP email logs over the network; if password reset emails are present, this enables account takeover.

If you're affected

  • Account takeover via reset links
  • Password reset link disclosure
  • Email confidentiality breach
  • Service disruption from locked accounts

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

60% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 233 days, from the signal feeds we watch.

  1. EPSS band changemoderate → high
  2. Nuclei check added
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Post SMTP, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store