YaysmtpWordPress extension · Yaycommerce
CVE-2025-0918
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 · uneditedThe SMTP for SendGrid – YaySMTP plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.4 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 confidenceThe YaySMTP WordPress plugin fails to properly sanitize user inputs and escape outputs, allowing unauthenticated attackers to inject malicious JavaScript code that gets stored in the database. This stored XSS executes whenever users access affected 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
< 1.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify YaySMTP plugin is installedNavigate to WordPress admin > Plugins or check the /wp-content/plugins/yaysmtp directory existsAffected if Plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > YaySMTP and read the version number displayedAffected if Version is lower than 1.4 (e.g., 1.3, 1.2, etc.)
-
Check if plugin is activeIn WordPress admin > Plugins, verify YaySMTP shows as 'Active'Affected if Plugin is active and version is below 1.4
-
Inspect database for injected scriptsQuery the wp_options table (or options table) for rows where option_name contains yaysmtp or yaysmtp_ and option_value contains script tags, iframe tags, or javascript: URIsAffected if Any option values contain unsanitized script or iframe tags from unauthenticated sources
A user is affected if YaySMTP plugin is installed, active, and running at version below 1.4, or if suspicious script injections are found in the plugin's database settings.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.4
Update to the latest version of YaySMTP plugin which includes proper input sanitization and output escaping. If no update is available, disable the plugin until a patched version is released.
Version 1.5 or latest available (any version > 1.4)
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the YaySMTP (or SMTP for SendGrid – YaySMTP) plugin
- Check the current version number
- If version is 1.4 or lower, click 'Update Now' to upgrade to the latest version
- Alternatively, download the latest version from wordpress.org/plugins/yaysmtp and upload via Plugins > Add New > Upload Plugin
- After update, verify the new version number in the plugins list
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Yaysmtp
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0918 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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