dbcve.org
Wp Mail SmtpWordPress extension · Wpforms

CVE-2023-3213

MEDIUM · 5.3 CVSS v3.1 Published 2023-10-04
Fix available
A fix is available. Upgrade to after 3.8.0 or later.
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
The WP Mail SMTP Pro plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the is_print_page function in versions up to, and including, 3.8.0. This makes it possible for unauthenticated attackers to disclose potentially sensitive email information.

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 WP Mail SMTP Pro plugin for WordPress versions up to 3.8.0 contains a broken access control vulnerability in the is_print_page function. This function lacks proper capability checks, allowing unauthenticated attackers to access sensitive email information that should require authorization.

MitigationUpgrade WP Mail SMTP Pro to version 3.8.1 or later which includes proper capability validation. Until then, consider restricting access to the affected endpoint via web server configuration or WAF rules.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Mail SmtpWordPress extension
Affected:<= 3.8.0

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Confirm WP Mail SMTP Pro is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the wp-mail-smtp folder, or list installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder wp-mail-smtp exists in the plugins directory
  2. Identify the installed version
    Open the main plugin file (wp-mail-smtp/wp-mail-smtp.php) and locate the 'Version' header in the plugin comment block, or check the version constant in the plugin bootstrap file
    Affected if The reported version is 3.8.0 or lower (any version up to and including 3.8.0)
  3. Verify the is_print_page function exists
    Search the plugin source code for the is_print_page function definition in files such as wp-mail-smtp/wp-mail-smtp.php or related class files
    Affected if The function is present in the plugin code, indicating the vulnerable code path exists
  4. Confirm the endpoint is accessible without authentication
    Attempt to access the print-friendly page endpoint that uses the is_print_page function (typically a URL containing /print/ or similar print-related path handled by the plugin) without providing any authentication credentials
    Affected if The endpoint returns content without requiring login or capability validation, meaning unauthenticated access is possible

If WP Mail SMTP Pro is installed with version 3.8.0 or lower and the print page endpoint is accessible without authentication, the environment is affected by CVE-2023-3213

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
Upgrade available Upgrade to a release after 3.8.0
Interim mitigation

Upgrade WP Mail SMTP Pro to version 3.8.1 or later which includes proper capability validation. Until then, consider restricting access to the affected endpoint via web server configuration or WAF rules.

Recommended fix Moderate confidence

Latest WP Mail SMTP Pro version (version > 3.8.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP Mail SMTP Pro
  4. Check if an update is available and update to the latest version (version > 3.8.0)
  5. Alternatively, download the latest version from wpmailsmtp.com and upload via Plugins > Add New > Upload Plugin
  6. Verify the update was successful by checking the plugin version

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

Fix this in Wp Mail Smtp Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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