dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67563

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in Saad Iqbal Post SMTP post-smtp allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Post SMTP: from n/a through <= 3.6.1.

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 · moderate confidence

Missing authorization vulnerability in the Post SMTP WordPress plugin allows exploitation of incorrectly configured access control security levels, likely enabling authenticated users with lower privileges to access or perform actions that should be restricted to higher-privileged roles.

MitigationUpdate Post SMTP plugin to the latest version which should include proper authorization checks, and audit WordPress user role capabilities to ensure proper access controls are enforced.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

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 installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Post SMTP. Note the version number displayed. Alternatively, check the plugin files in wp-content/plugins/post-smtp/ for a version marker or query the WordPress plugins API.
    Affected if Post SMTP is installed and the version falls within the affected range (compare your installed version to the latest version, as the vulnerability exists in versions lacking proper authorization checks)
  2. Identify WordPress user roles with access
    Navigate to Users > All Users in the WordPress admin dashboard. Review the role assigned to each user account (Administrator, Editor, Author, Contributor, Subscriber).
    Affected if There are users assigned to roles below Administrator (such as Editor, Author, Contributor, or Subscriber) who should not have access to plugin settings
  3. Check Post SMTP capability configuration
    Inspect the Post SMTP plugin configuration by accessing Post SMTP > Settings or similar menu options. Determine which WordPress roles can access or modify plugin settings, particularly mail sending configurations and API keys.
    Affected if The plugin allows users with roles other than Administrator to access or modify mail settings, API credentials, or sending configurations
  4. Review role capability assignments
    Use a role management plugin or WordPress REST API to query capability assignments: GET /wp-json/wp/v2/users?per_page=100 and examine the capabilities field for each user, or inspect wp_usermeta for meta_key like wp_capabilities.
    Affected if Users with lower-privileged roles (subscriber, contributor, author) possess capabilities that should be restricted to administrators (such as manage_options, edit_users, or plugin-specific capabilities)
  5. Audit access to sensitive plugin functions
    Test whether lower-privileged users can access Post SMTP admin pages directly via URL or trigger mail-sending functions through WordPress AJAX endpoints (admin-ajax.php) with action parameters related to Post SMTP.
    Affected if Lower-privileged authenticated users can directly access plugin admin pages or execute mail-related AJAX actions without proper authorization checks

A user is affected if Post SMTP plugin is installed and allows users with non-Administrator roles to access or modify plugin settings or mail-sending functionality.

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

Update Post SMTP plugin to the latest version which should include proper authorization checks, and audit WordPress user role capabilities to ensure proper access controls are enforced.

Recommended fix Moderate confidence

Latest available version of Post SMTP (newer than 3.6.1)

  1. Check the WordPress admin dashboard for available plugin updates
  2. Update Post SMTP plugin to the latest available version from the WordPress plugin repository
  3. Verify the update was successful by confirming the new version number in the plugins list
  4. Test that SMTP functionality continues to work correctly after the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67563 — 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-67563 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