VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

YaySMTP – Simple WP SMTP Mail <= 2.2 — Sensitive Information Disclosure

CVE-2022-2369Published · Updated

Action summary

Affected: 2.2 – 2.2Update to 2.2.1 or newer

All remediation steps
Watch plugin
Severity
High7.5
CVSS
7.5
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:N Integrity
None
A:N Availability
None
Weakness
CWE-200 Information Exposure
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports yaysmtp

  1. Affected2.2 – 2.2
  2. Patched in2.2.1

Update to 2.2.1 or newer.

You are affected if you run 2.2 – 2.2. Version 2.2.1 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.2.1, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Rafshanzani Suhada.

The YaySMTP WordPress plugin before 2.2.1 does not have capability check in an AJAX action, allowing any logged in users, such as subscriber to view the logs of the plugin

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

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

All 10
More vulnerabilities in YaySMTP – WP Mail SMTP with Email Logs, Tracking & Reports
SeverityVulnerabilityCVEPublished
Medium4.9Authenticated (Administrator+) SQL Injection via 'params[searchKey]' Parameter
≤2.7.8Update to 2.7.9
CVE-2026-109977
High8.8Authenticated (Subscriber+) Arbitrary File Upload via Attachment Filename Extension
≤2.7.7Update to 2.7.8
CVE-2026-92553
Medium4.9Authenticated (Administrator+) SQL Injection
≤2.6.6Update to 2.6.7
CVE-2025-53256
Medium4.9Authenticated (Administrator+) SQL Injection
≤2.6.4Update to 2.6.5
CVE-2025-47587
High7.22.6.3 - Unauthenticated Stored Cross-Site Scripting
2.4.9 – 2.6.3Update to 2.6.4
CVE-2025-0916

Same weakness (Information Exposure)

All Information Exposure
Other Information Exposure vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent Header
EZ SQL Reports Shortcode Widget and DB Backup≤5.25.25Update to 5.26.45
CVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form Submission
Chatterbug Forms – Fast, Flexible WordPress Form Builder≤1.0.2Update to 1.1
CVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' Parameter
ELEX WordPress HelpDesk & Customer Ticketing System≤3.3.9Update to 3.4.0
CVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 7.5

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?