dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-49288

HIGH · 8.8 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
Missing Authorization vulnerability in Rustaurius Ultimate WP Mail ultimate-wp-mail allows Authentication Bypass.This issue affects Ultimate WP Mail: from n/a through <= 1.3.5.

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

The Ultimate WP Mail WordPress plugin has a missing authorization vulnerability that allows attackers to bypass authentication mechanisms. This enables unauthenticated users to potentially access administrative functions or sensitive mail-related operations that should require valid credentials.

MitigationUpdate Ultimate WP Mail to the latest version immediately. If no patched version is available, restrict access to the plugin's endpoints at the web server level (e.g., via .htaccess or firewall rules) until a fix is released.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Ultimate WP Mail plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Ultimate WP Mail' in the installed plugins list. Note whether it is activated.
    Affected if The Ultimate WP Mail plugin is installed and active on the WordPress site.
  2. Identify the installed version of Ultimate WP Mail
    In the Plugins list, find Ultimate WP Mail and view the version number displayed beneath the plugin name. Alternatively, access the plugin files via FTP or file manager and check the main plugin file header for the Version field.
    Affected if The installed version matches or predates any vulnerable version of the plugin (compare your version to the vendor's release notes for security patches).
  3. Test plugin endpoints for missing authorization
    Use a tool like Burp Suite or curl to send requests to common WordPress admin AJAX endpoints (e.g., /wp-admin/admin-ajax.php) and the Ultimate WP Mail specific endpoints without providing authentication cookies or credentials. Check if the requests are processed without returning an authentication error.
    Affected if Requests to administrative or mail-related plugin endpoints succeed without requiring valid authentication credentials.
  4. Review access logs for unauthenticated plugin access
    Examine the web server access logs (Apache error.log, Nginx access.log) and WordPress activity logs for repeated requests to plugin-related URLs or admin-ajax.php actions originating from unauthenticated IP addresses.
    Affected if Logs show requests to plugin functions or admin areas that were made without corresponding authenticated sessions.
  5. Check for unauthorized mail configuration changes
    Inspect the Ultimate WP Mail settings in the WordPress admin panel (if accessible) or directly review the wp_options database table for any unexpected modifications to mail configuration, particularly values related to SMTP settings, sender addresses, or mail routing.
    Affected if Mail settings have been altered without an authenticated admin session, or configuration changes cannot be traced to legitimate administrator actions.

The site is affected if the Ultimate WP Mail plugin is installed and its administrative or mail-related endpoints can be accessed or manipulated without valid authentication credentials.

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 the latest version immediately. If no patched version is available, restrict access to the plugin's endpoints at the web server level (e.g., via .htaccess or firewall rules) until a fix is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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