LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3093: YaySMTP <= 2.4.5 - Unauthenticated Stored Cross-Site Scripting via Email

The YaySMTP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via email contents in versions up to, and including, 2.4.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

YaySMTP for WordPress allowed unsafe email content to be stored and later rendered as script. An outside attacker could potentially cause malicious JavaScript to run in the browser of someone viewing the affected page. For a business, the concern is account-session risk and trust impact on affected WordPress administration workflows.

Executive priority

Treat this as a high-priority WordPress plugin remediation item, especially on customer-facing or business-critical sites. The bundle does not prove exploitation, but unauthenticated stored XSS can create meaningful account and content-integrity risk if administrators view affected stored content.

Technical view

CVE-2023-3093 is stored cross-site scripting in YaySMTP versions up to and including 2.4.5, caused by insufficient input sanitization and output escaping of email contents. The CVSS 3.1 score is 7.2, network exploitable, low complexity, unauthenticated, with changed scope and low confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to WordPress sites running YaySMTP at version 2.4.5 or earlier. Sites not using this plugin, or using versions beyond the affected range, are not indicated as exposed by the source bundle.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The risk comes from unauthenticated stored XSS: malicious script may execute when a user accesses a page containing stored email content.

Researcher notes

The provided data identifies CWE-79 and points to a WordPress.org changeset, but does not include detailed patch notes or exploit telemetry. Avoid assuming active exploitation. Validation should focus on plugin presence, version, exposed email-content rendering, and post-remediation review of stored content.

Mitigation direction

  • Inventory WordPress sites for YaySMTP installations and installed versions.
  • Update YaySMTP beyond version 2.4.5 where vendor guidance confirms a fixed release.
  • Disable or remove the plugin if timely update is not possible.
  • Restrict access to WordPress administration until remediation is complete.
  • Review vendor and Wordfence guidance for any additional cleanup instructions.

Validation and detection

  • Confirm whether YaySMTP is installed on each WordPress site.
  • Record the installed plugin version and compare it to 2.4.5.
  • Review WordPress users and sessions for suspicious administrative activity.
  • Inspect plugin email-log views for unexpected script-like content.
  • Verify remediation by confirming the plugin is updated or removed.
Prepared
Confidence
high
Sources
4

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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2023-3093 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
7.2 (3.1)
Known Exploited
No
Published

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

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
3Source 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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2023-3093Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
yaycommerceYaySMTP and Email Logs: Amazon SES, SendGrid, Outlook, Mailgun, Brevo, Google and Any SMTP Service0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.