Easy Wp SmtpWordPress extension · Wp Ecommerce
CVE-2022-45829
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 · uneditedAuth. Path Traversal vulnerability in Easy WP SMTP plugin <= 1.5.1 at 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 confidenceAuthenticated path traversal vulnerability in Easy WP SMTP plugin <= 1.5.1 allows attackers with user-level access to manipulate file path references and potentially read sensitive files outside the web root directory.
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
<= 1.5.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Easy WP SMTP plugin is installedCheck the WordPress plugins directory or access the plugin admin page to verify Easy WP SMTP is present and activeAffected if The plugin is installed and active in WordPress
-
Identify installed Easy WP SMTP versionAccess the WordPress admin dashboard under Plugins > Installed Plugins and locate the Easy WP SMTP plugin to view its version number, or check the plugin header in its main PHP fileAffected if The installed version is 1.5.1 or lower
-
Verify user authentication is possibleReview WordPress user accounts and check if any accounts exist with subscriber-level access or higher, as the vulnerability requires authenticated user-level accessAffected if Any user account (even low-privilege) can access the vulnerable endpoint
-
Check for suspicious file access attemptsReview web server access logs and WordPress audit logs for unusual requests to the plugin's endpoints that include directory traversal patterns (such as ../ or absolute paths to system files)Affected if Logs show requests to Easy WP SMTP endpoints with path traversal sequences accessing files outside the web root
You are affected if Easy WP SMTP plugin version 1.5.1 or lower is installed, any authenticated user account exists, and the plugin's file handling feature is accessible, or if exploitation indicators are present in logs.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Easy WP SMTP plugin to a version greater than 1.5.1, and verify that email functionality continues to work correctly after the update.
Fix this in Easy Wp Smtp
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-45829 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45829 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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