Easy Wp SmtpWordPress extension · Wp Ecommerce
CVE-2022-42699
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. Remote Code Execution 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 confidenceAn authenticated remote code execution vulnerability exists in the Easy WP SMTP WordPress plugin versions 1.5.1 and below. Attackers with valid user credentials can potentially execute arbitrary code on the affected WordPress installation through this 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
<= 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Check Easy WP SMTP plugin versionLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate Easy WP SMTP, and read the version number displayed below the plugin name. Alternatively, inspect the plugin file /wp-content/plugins/easy-wp-smtp/easy-wp-smtp.php and look for the 'Version' header in the plugin comment block.Affected if The displayed version is 1.5.1 or lower (e.g., 1.5.0, 1.4.9, etc.)
-
Confirm plugin is activeIn the WordPress admin under Plugins > Installed Plugins, verify that Easy WP SMTP shows as 'Active' rather than 'Inactive' or 'Not installed'.Affected if The plugin is installed and currently active.
-
Check for accessible admin accountsNavigate to Users > All Users in the WordPress admin dashboard and review which user accounts have administrator-level privileges or access to the Easy WP SMTP settings. An attacker needs valid credentials to exploit this vulnerability.Affected if There are active user accounts with administrative or editor-level access to the WordPress site.
You are affected if the Easy WP SMTP plugin version is 1.5.1 or lower AND the plugin is active AND there are valid user credentials that could be used to access the WordPress admin area.
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.
dbcve · scopedUpdate the Easy WP SMTP plugin to a version newer than 1.5.1. If an updated version is unavailable, disable or remove the plugin until a patch is released.
Easy WP SMTP version 1.5.2 or higher
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the Easy WP SMTP plugin
- Check the current installed version (should be <= 1.5.1)
- Click 'Update Now' if an update is available, or manually download version 1.5.2 or higher from the WordPress plugin repository
- If automatic update fails, delete the existing plugin and upload/install version 1.5.2 or higher
- Verify the update was successful by checking the plugin version after updating
- Ensure the plugin is activated if it was deactivated during the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Easy Wp Smtp
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42699 — 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-42699 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