dbcve.org
YaysmtpWordPress extension · Yaycommerce

CVE-2025-0953

MEDIUM · 6.1 CVSS v3.1 Published 2025-02-22
Fix available
A fix is available. Upgrade to 1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The YaySMTP WordPress plugin versions up to 1.2 contains a stored XSS vulnerability where unauthenticated attackers can inject malicious JavaScript through insufficiently sanitized input fields. The injected scripts persist on the server and execute when administrative users or other site visitors access affected pages, potentially leading to session hijacking or privilege escalation.

MitigationUpdate the YaySMTP plugin to the latest version which includes proper input sanitization and output escaping. Until then, consider disabling the plugin or restricting access to settings pages.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
YaysmtpWordPress extension
Affected:< 1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify YaySMTP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Yaysmtp' or 'YaySMTP' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'yaysmtp' or similar.
    Affected if The YaySMTP plugin folder exists in the WordPress plugins directory.
  2. Check installed YaySMTP version
    In WordPress admin, go to Plugins > Installed Plugins and find the YaySMTP entry. The version number is displayed below the plugin name. Alternatively, check the main plugin file (e.g., yaysmtp.php) for the 'Version' header comment.
    Affected if The installed version is 1.2 or lower, or if no version number is displayed and the plugin appears to be the pre-update release.
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, check if YaySMTP shows 'Active' status or a green activation indicator.
    Affected if The plugin is active and processing email settings.
  4. Identify accessible SMTP settings pages
    Navigate to the YaySMTP settings page (usually under Settings > YaySMTP or a dedicated YaySMTP menu item). Look for input fields related to SMTP configuration such as 'From Name', 'From Email', 'SMTP Host', 'SMTP Username', or similar fields.
    Affected if The SMTP settings form with input fields is accessible, indicating the vulnerable code is in use.
  5. Review recent plugin activity logs
    Check WordPress debug logs or server access logs for any unusual POST requests to /wp-admin/admin-ajax.php or the YaySMTP settings endpoint that might contain suspicious script tags in parameter values.
    Affected if Unusual or malicious input patterns are found in logs related to YaySMTP functionality.

You are affected if the YaySMTP plugin is installed, active, and running version 1.2 or lower, with accessible SMTP configuration input fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2 or later
Fixed in 1.2
Interim mitigation

Update the YaySMTP plugin to the latest version which includes proper input sanitization and output escaping. Until then, consider disabling the plugin or restricting access to settings pages.

Recommended fix Moderate confidence

YaySMTP version 1.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the YaySMTP (SMTP for Sendinblue) plugin
  4. 4. Check the current installed version
  5. 5. If the installed version is below 1.2, update the plugin to version 1.2 or later
  6. 6. Alternatively, navigate to Dashboard > Updates and update all plugins, which will include YaySMTP if an update is available
  7. 7. After updating, verify the fix by confirming the plugin version is 1.2 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Yaysmtp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0953 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0953 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data