CVE-2025-0953: SMTP for Sendinblue – YaySMTP <= 1.2 - Unauthenticated Stored Cross-Site Scripting via Email Logs
The SMTP for Sendinblue – YaySMTP plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.2 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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-0953 affects the WordPress plugin SMTP for Sendinblue – YaySMTP through version 1.2. An unauthenticated attacker could store malicious script in email log content, which may execute when a site user views the affected page. This creates risk of account compromise or unauthorized actions in WordPress admin context.
Executive priority
Treat this as a prompt WordPress hygiene item. The issue is high severity and unauthenticated, but current sources do not show confirmed active exploitation. Prioritize internet-facing WordPress sites and environments where WordPress admins have privileged access.
Technical view
The issue is stored cross-site scripting caused by insufficient input sanitization and output escaping in YaySMTP email-log handling. It is tracked as CWE-79 with CVSS 3.1 score 7.2. Sources identify affected versions up to and including 1.2; no active exploitation evidence is provided.
Likely exposure
Exposure is likely limited to WordPress sites running SMTP for Sendinblue – YaySMTP version 1.2 or earlier with email logging reachable through the vulnerable code path.
Exploitation context
The CVE record states unauthenticated attackers can inject stored scripts. The bundle does not include KEV listing or other evidence of active exploitation, so exploitation in the wild is unconfirmed from these sources.
Researcher notes
Focus analysis on email-log storage and rendering paths. The referenced WordPress Trac files and changeset are useful for confirming sanitization and escaping changes. Avoid assuming fixed-version details beyond the sourced affected range unless vendor metadata confirms them.
Mitigation direction
Identify sites running SMTP for Sendinblue – YaySMTP.
Upgrade beyond version 1.2 if a vendor-supported patched release is available.
Disable or remove the plugin if no safe update is available.
Restrict WordPress administrative access to trusted users and networks.
Review vendor and WordPress plugin guidance for the confirmed fixed version.
Validation and detection
Inventory WordPress plugins and record YaySMTP versions.
Confirm whether any installation is version 1.2 or earlier.
Review email logs for unexpected script-like content without executing it.
Verify the plugin update history against WordPress.org or vendor guidance.
Confirm administrative pages properly escape stored log output after remediation.
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.
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.
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.
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.