dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12887

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. CVE-2025-67563 appears to be a duplicate of this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Post SMTP WordPress plugin fails to perform proper authorization checks in the handle_gmail_oauth_redirect function, allowing any authenticated user with subscriber-level access or higher to modify OAuth tokens. This broken access control vulnerability enables attackers to inject attacker-controlled or invalid OAuth credentials into the plugin's configuration.

MitigationUpgrade to Post SMTP version 3.6.2 or later which contains proper authorization validation. Until then, restrict user registration and monitor for suspicious OAuth configuration changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Post SMTP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Post SMTP' in the list. Note the version number displayed under the plugin name.
    Affected if Post SMTP is installed and the displayed version is lower than 3.6.2
  2. Check WordPress user roles with access
    Navigate to Users > All Users in WordPress admin. Review the role assigned to each user account. Look for any accounts with Subscriber, Contributor, Author, Editor, or Administrator roles.
    Affected if There is at least one user account with Subscriber-level access or higher (which includes all standard roles)
  3. Confirm Gmail OAuth feature is configured
    Go to Post SMTP > Gmail OAuth Settings (or similar OAuth configuration page in the plugin). Check if any Gmail/Google OAuth credentials are configured or if the feature is enabled.
    Affected if Gmail OAuth is configured or enabled - the vulnerability allows modification of these OAuth tokens
  4. Inspect OAuth redirect handler configuration
    Access the plugin files via FTP or file manager. Locate the handle_gmail_oauth_redirect function in the plugin code (typically in includes/ or src/ folders). Check if the function lacks capability checks or role validation before processing the redirect.
    Affected if The function processes OAuth redirects without verifying user permissions (e.g., missing current_user_can() check)
  5. Review recent OAuth configuration changes
    If activity logging is enabled, check Post SMTP logs or WordPress audit logs for any recent modifications to OAuth settings, token updates, or Gmail connection configurations that were not performed by administrators.
    Affected if OAuth configuration changes exist that were made by non-admin users or without proper authorization

A user is affected if Post SMTP version is below 3.6.2 AND the Gmail OAuth feature is enabled AND there exists at least one user with Subscriber-level access or higher who could exploit the broken access control.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Post SMTP version 3.6.2 or later which contains proper authorization validation. Until then, restrict user registration and monitor for suspicious OAuth configuration changes.

Recommended fix High confidence

Post SMTP version 3.6.2 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Post SMTP plugin
  4. Click 'Update now' if an update is available, or manually update to version 3.6.2 or higher
  5. Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12887 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12887 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data