dbcve.org
Easy Wp SmtpWordPress extension · Wp Ecommerce

CVE-2022-45833

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-06
Fix available
A fix is available. Upgrade to after 1.5.1 or later.
See remediation →
71/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
Auth. Path Traversal vulnerability in Easy WP SMTP plugin <= 1.5.1 on WordPress.

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

Authenticated path traversal vulnerability in Easy WP SMTP plugin versions 1.5.1 and below allows authenticated attackers to access sensitive files outside the web root directory via directory traversal sequences in plugin parameters.

MitigationUpdate Easy WP SMTP plugin to version 1.5.2 or later to patch the vulnerability.

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
Easy Wp SmtpWordPress extension
Affected:<= 1.5.1

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Verify Easy WP SMTP plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Easy WP SMTP' in the plugin list.
    Affected if Plugin is not installed or not found in the list.
  2. Check installed plugin version
    In the plugins list, locate Easy WP SMTP and note the version number displayed beneath the plugin name. Alternatively, check the plugin's main PHP file header for the Version field.
    Affected if Version is 1.5.1 or lower.
  3. Confirm plugin is active
    In the plugins list, verify that Easy WP SMTP shows as 'Active' under the plugin status column.
    Affected if Plugin is active and accessible.
  4. Check for user accounts with access to plugin settings
    Review WordPress user roles. The vulnerability requires an authenticated attacker, so check which user accounts exist with administrative or editor-level access who can reach the plugin settings page (Easy WP SMTP settings).
    Affected if Any authenticated user account exists with access to the plugin configuration.

Your environment is affected if Easy WP SMTP plugin version 1.5.1 or lower is installed and active, with at least one authenticated user able to access the plugin settings parameters.

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.

From vendor data
Upgrade available Upgrade to a release after 1.5.1
Interim mitigation

Update Easy WP SMTP plugin to version 1.5.2 or later to patch the vulnerability.

Fix this in Easy Wp Smtp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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