dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-47587

HIGH · 7.6 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in YayCommerce YaySMTP yaysmtp allows Blind SQL Injection.This issue affects YaySMTP: from n/a through <= 2.6.4.

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 · moderate confidence

A blind SQL injection vulnerability exists in the YayCommerce YaySMTP WordPress plugin (versions <= 2.6.4) where user-supplied input is not properly neutralized before being used in SQL queries, allowing authenticated attackers to inject malicious SQL commands and potentially extract sensitive data from the database.

MitigationUpdate YaySMTP to the latest patched version immediately; if unavailable, implement proper input sanitization and parameterized queries at the vulnerable entry point, and consider deploying a WAF as an interim protective control.

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

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for YaySMTP or YayCommerce YaySMTP in the list
    Affected if The plugin appears in the installed plugins list
  2. Check YaySMTP version number
    Click on the plugin name/details or view the plugin header in wp-content/plugins/yaysmtp/yaysmtp.php to find the Version: field
    Affected if The version number is 2.6.4 or lower
  3. Confirm user registration or admin access exists
    Review WordPress general settings for "Membership" (anyone can register) or check if there are existing user accounts beyond the administrator
    Affected if User registration is enabled or there are user accounts other than the primary admin that could potentially have access to the plugin settings
  4. Review access logs for SQL injection patterns
    Examine web server access logs and WordPress debug logs for unusual query strings containing SQL keywords (SELECT, UNION, WHERE) passed to YaySMTP-related URLs
    Affected if Suspicious SQL-like patterns appear in requests to the plugin

You are affected if YaySMTP is installed with version 2.6.4 or lower and any authenticated user account exists on the WordPress site.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update YaySMTP to the latest patched version immediately; if unavailable, implement proper input sanitization and parameterized queries at the vulnerable entry point, and consider deploying a WAF as an interim protective control.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47587 — 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-47587 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