dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-47466

MEDIUM · 5.4 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 →
61/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
Cross-Site Request Forgery (CSRF) vulnerability in Rustaurius Ultimate WP Mail ultimate-wp-mail allows Cross Site Request Forgery.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

Cross-Site Request Forgery (CSRF) vulnerability in the Ultimate WP Mail WordPress plugin (versions up to 1.3.4) allows attackers to trick authenticated administrators into performing unintended state-changing actions. The plugin lacks proper nonce verification on sensitive operations, enabling attackers to craft malicious requests that execute with the victim's authenticated session.

MitigationImplement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all state-changing forms and AJAX endpoints, and add SameSite cookie attributes to session cookies.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find 'Ultimate WP Mail', and check the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/ultimate-wp-mail/) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 1.3.4 or lower (including any 1.x.x release).
  2. Identify state-changing plugin functions
    Review the plugin's PHP files for AJAX handlers (wp_ajax_* hooks), form processing code, and any functions that modify data, send emails, or change settings. Look for files like ultimate-wp-mail.php or any file in an /includes/ or /admin/ folder.
    Affected if The plugin contains forms, AJAX endpoints, or admin actions that perform state-changing operations.
  3. Inspect for nonce verification absence
    Search the plugin PHP files for 'wp_verify_nonce', 'check_admin_referer', or 'wp_create_nonce'. Examine the identified state-changing handlers (AJAX, form processors) to see if they verify nonces before executing sensitive operations.
    Affected if State-changing handlers do NOT contain wp_verify_nonce, check_admin_referer, or similar nonce verification calls before processing requests.
  4. Verify admin authentication requirement
    Check if the identified vulnerable endpoints use current_user_can() or require 'manage_options' capability before executing sensitive actions. Review the capability checks in AJAX handlers and form processors.
    Affected if The plugin lacks proper capability checks (current_user_can) on sensitive operations, allowing lower-privilege authenticated users to be exploited.

A user is affected if they have Ultimate WP Mail plugin version 1.3.4 or lower installed AND the plugin's sensitive operations (forms, AJAX endpoints) lack proper nonce verification and capability checks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all state-changing forms and AJAX endpoints, and add SameSite cookie attributes to session cookies.

Recommended fix Moderate confidence

Latest version of Ultimate WP Mail available from the vendor (contact vendor or check WordPress plugin repository for version newer than 1.3.4)

  1. Check the WordPress plugin repository or contact the vendor (Rustaurius) to obtain the latest version of Ultimate WP Mail that addresses the CSRF vulnerability
  2. Verify the installed version of Ultimate WP Mail is below the fixed release before updating
  3. Update the plugin to the latest available version from the official WordPress plugin repository or vendor
  4. After updating, confirm the plugin functions correctly and test the affected functionality
  5. Ensure WordPress core and all other plugins are also kept up to date

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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