Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12887: CWE-862 Missing Authorization in saadiqbal Post SMTP – Complete SMTP Solution with Logs, Alerts, Backup SMTP & Mobile App

0
Medium
VulnerabilityCVE-2025-12887cvecve-2025-12887cwe-862
Published: Wed Dec 03 2025 (12/03/2025, 12:29:53 UTC)
Source: CVE Database V5
Vendor/Project: saadiqbal
Product: Post SMTP – Complete SMTP Solution with Logs, Alerts, Backup SMTP & Mobile App

Description

The Post SMTP plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.6.1. This is due to the plugin not properly verifying that a user is authorized to update OAuth tokens on the 'handle_gmail_oauth_redirect' function. This makes it possible for authenticated attackers, with subscriber level access and above, to inject invalid or attacker-controlled OAuth credentials.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 21:18:06 UTC

Technical Analysis

CVE-2025-12887 is a medium-severity authorization bypass vulnerability affecting the Post SMTP plugin for WordPress, versions up to and including 3.6.1. The root cause is the plugin's failure to properly verify that a user is authorized to update OAuth tokens within the 'handle_gmail_oauth_redirect' function. This flaw allows any authenticated user with subscriber-level privileges or higher to inject invalid or attacker-controlled OAuth credentials. Since WordPress subscriber roles typically have limited capabilities, this vulnerability significantly lowers the bar for exploitation compared to requiring administrator privileges. The injected OAuth credentials could be used to disrupt legitimate email sending, cause denial of service, or potentially facilitate further attacks by manipulating SMTP authentication flows. The vulnerability is network exploitable (AV:N), requires low privileges (PR:L), does not require user interaction (UI:N), and affects the integrity and availability of the email system (I:L, A:L), resulting in a CVSS 3.1 base score of 5.4. No patches or exploits are currently publicly available, but the vulnerability is published and should be addressed promptly. The plugin is widely used in WordPress environments for SMTP email delivery, making this a relevant threat for many organizations relying on WordPress for web presence and communications.

Potential Impact

The primary impact of this vulnerability is on the integrity and availability of email services managed through the Post SMTP plugin. Attackers with subscriber-level access can inject malicious OAuth tokens, potentially disrupting email delivery or redirecting emails through attacker-controlled accounts. This can lead to denial of service for legitimate email communications, loss of trust in email authenticity, and potential escalation paths if attackers leverage the compromised OAuth tokens for further access. Organizations relying on this plugin for critical email functions may experience operational disruptions. Additionally, the ease of exploitation by low-privilege users increases the risk of insider threats or compromised low-level accounts being leveraged to cause damage. Although confidentiality is not directly impacted, the manipulation of OAuth credentials could indirectly facilitate phishing or social engineering attacks if attackers control outbound email flows. The lack of known exploits in the wild reduces immediate risk but does not eliminate the potential for future exploitation.

Mitigation Recommendations

To mitigate this vulnerability, organizations should immediately upgrade the Post SMTP plugin to a patched version once available. In the absence of a patch, restrict subscriber-level user permissions to the minimum necessary and audit existing users for suspicious accounts. Implement strict role-based access controls to prevent unauthorized users from accessing or modifying OAuth token settings. Monitor logs for unusual changes to OAuth credentials or SMTP configurations. Consider disabling the plugin temporarily if email delivery can be managed through alternative secure methods. Employ multi-factor authentication (MFA) for all WordPress accounts to reduce the risk of account compromise. Additionally, review and harden OAuth token management workflows and validate all token updates server-side to ensure proper authorization. Regularly back up WordPress configurations and email settings to enable quick recovery if exploitation occurs.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-07T17:28:03.418Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69302ef1720cedca7945237d

Added to database: 12/3/2025, 12:37:05 PM

Last enriched: 2/27/2026, 9:18:06 PM

Last updated: 3/24/2026, 11:38:41 PM

Views: 124

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses