dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-47490

HIGH · 8.5 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 →
91/100
Remediation priority · Urgent
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 Rustaurius Ultimate WP Mail ultimate-wp-mail allows SQL Injection.This issue affects Ultimate WP Mail: from n/a through <= 1.3.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

SQL Injection vulnerability in the Ultimate WP Mail WordPress plugin allows attackers to inject malicious SQL commands via unsanitized input in affected parameters. This could enable unauthorized data access, modification, or potentially remote code execution depending on database privileges.

MitigationUpdate Ultimate WP Mail to a patched version beyond 1.3.4, or apply secure coding practices (parameterized queries/prepared statements) to all database interactions in the plugin code.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Ultimate WP Mail plugin is installed
    Log into WordPress admin, go to Plugins > Installed Plugins, and search for 'Ultimate WP Mail' or check the plugins directory via FTP for /wp-content/plugins/ultimate-wp-mail/
    Affected if The plugin is present in the plugins directory regardless of activation status
  2. Determine installed plugin version
    In WordPress admin, find Ultimate WP Mail in the plugins list and read the version number displayed below the plugin name, or open the main plugin file (usually ultimate-wp-mail.php) and look for the 'Version:' header in the plugin comments
    Affected if Version is 1.3.4 or lower (the vulnerability is present up to and including 1.3.4)
  3. Confirm plugin is actively used
    Check if the plugin is activated in WordPress admin > Plugins, or if any shortcode (such as [ultimate_wp_mail] or similar) is present in published posts/pages, or if the plugin's mail capture form is displayed on the site
    Affected if Plugin is activated or its shortcodes/forms are embedded in site content, enabling the vulnerable code paths
  4. Inspect database interaction points
    Review the plugin's PHP files in /wp-content/plugins/ultimate-wp-mail/ for direct SQL queries using $wpdb->prepare without proper sanitization, or search for SQL query patterns where user input (like $_POST, $_GET, or $_REQUEST variables) flows into raw SQL statements
    Affected if Direct SQL queries exist without prepared statements and user-supplied parameters are passed unsanitized to the database
  5. Check for unauthorized database anomalies
    Query the WordPress database for any unexpected new tables or modified records in wp_posts, wp_users, or wp_options that may indicate exploitation, using: SELECT * FROM wp_posts WHERE post_content LIKE '%sql_injection_test%' or reviewing database logs for unusual queries
    Affected if Unexpected database changes or suspicious query patterns appear in logs or database tables

Your environment is affected if the Ultimate WP Mail plugin is installed with version 1.3.4 or lower and the plugin is activated or its features are in use on the 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 Ultimate WP Mail to a patched version beyond 1.3.4, or apply secure coding practices (parameterized queries/prepared statements) to all database interactions in the plugin code.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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