LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45829: WordPress Easy WP SMTP Plugin <= 1.5.1 is vulnerable to Arbitrary File Deletion

Auth. Path Traversal vulnerability in Easy WP SMTP plugin <= 1.5.1 at WordPress.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects WordPress sites using Easy WP SMTP plugin version 1.5.1 or earlier. An authenticated high-privilege user could use path traversal to delete files, potentially disrupting the site or damaging integrity. The supplied sources do not show CISA KEV listing or active exploitation.

Executive priority

Treat as a high-priority WordPress hygiene issue, especially for business-critical sites. It is not confirmed actively exploited in the supplied sources, but the potential for file deletion can create downtime or integrity loss.

Technical view

CVE-2022-45829 is an authenticated CWE-22 path traversal issue in Easy WP SMTP <= 1.5.1 for WordPress, reported as arbitrary file deletion. CVSS 3.1 is 8.7: network exploitable, low complexity, high privileges required, no user interaction, changed scope, high integrity and availability impact.

Likely exposure

Exposure is likely limited to WordPress installations with Easy WP SMTP version 1.5.1 or earlier and accounts holding the required high privileges. The bundle provides no CPEs or fixed-version detail, so asset validation should use installed plugin versions and vendor guidance.

Exploitation context

The CVE is not marked KEV in the supplied bundle. No provided source states active exploitation. Risk remains material because a privileged authenticated actor could delete files without user interaction, affecting availability and integrity.

Researcher notes

Evidence supports authenticated arbitrary file deletion through path traversal in Easy WP SMTP <= 1.5.1. The supplied affected metadata lacks CPEs and fixed-version details. Avoid assuming unauthenticated impact or active exploitation without additional vendor or threat-intelligence confirmation.

Mitigation direction

  • Inventory WordPress sites for Easy WP SMTP and record installed versions.
  • Update or remove affected Easy WP SMTP installations according to vendor guidance.
  • Disable the plugin temporarily where update status cannot be confirmed.
  • Restrict high-privilege WordPress accounts to trusted users only.
  • Ensure recent site and file backups are available before remediation.

Validation and detection

  • Confirm whether Easy WP SMTP is installed and at version 1.5.1 or earlier.
  • Review WordPress admin users and other high-privilege accounts.
  • Check site file integrity and logs for unexpected file deletions.
  • Verify vendor or Patchstack guidance for the fixed version before closure.
  • Document remediation status for each affected WordPress site.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-45829 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H2.35.8Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.7High
CVSS 3.1 vector shape for CVE-2022-45829Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WPecommerce, AlexanderfoxcEasy WP SMTPn/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.