Post Smtp: A security weakness
Post Smtp is affected by a security weakness. Exploitation requires an authenticated subscriber account. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Post Smtp
- Plugin slug
post-smtp- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Sep 03, 2025
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Sep 03, 2025 and is one of 29 known issues for this plugin.
Update, patch or deactivate.
No fixed release is identified. Update Post Smtp when a confirmed fixed release becomes available; until then, disable and remove it when the site's risk warrants.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Post SMTP – WP SMTP Plugin with Email Logs and Mobile App for Failure Notifications – Gmail SMTP, Office 365, Brevo, Mailgun, Amazon SES and more plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'update_post_smtp_pro_option_callback' function in all versions up to, and including, 3.4.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to enable pro extensions.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N