CVE-2022-2370

YaySMTP – Simple WP SMTP Mail <= 2.2 - Missing Authorization to Sensitive Information Exposure

2022-07-11 00:00

Strategic Overview

Status: Patched in 2.2.1
Affected Plugin: YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports
Affected Version: <= 2.2
CVSS: 6.5Medium
Weakness type: CWE-862 · Missing Authorization
CVE: CVE-2022-2370

View all YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports vulnerabilities

At a glance

CVE-2022-2370 is a medium-severity Missing Authorization vulnerability in the YaySMTP WordPress plugin, affecting versions <= 2.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.2.1; sites on affected versions should update now. Disclosed July 2022.

Vulnerability Overview

The YaySMTP WordPress plugin before 2.2.1 does not have capability check before displaying the Mailer Credentials in JS code for the settings, allowing any authenticated users, such as subscriber to retrieve them

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-862: Missing Authorization

Reaching this weakness in YaySMTP <= 2.2 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For YaySMTP the fix is 2.2.1: builds <= 2.2 are affected, anything from 2.2.1 onward is not.

Remediation

Update to version 2.2.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: YaySMTP 2.2.1 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-2370 https://www.wordfence.com/threat-intel/vulnerabilities/id/4b68e8d4-58d4-4753-bda3-60c0d874f822 https://nvd.nist.gov/vuln/detail/CVE-2022-2370

Related records

Other vulnerabilities in YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports

CVSS Vector

6.5

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/