dbcve.org
WemailWordPress extension · Wedevs

CVE-2025-47540

HIGH · 7.5 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to 1.14.14 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in weDevs weMail wemail allows Retrieve Embedded Sensitive Data.This issue affects weMail: from n/a through <= 1.14.13.

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 weMail plugin for WordPress versions up to 1.14.13 contains an information disclosure vulnerability allowing unauthenticated attackers to retrieve embedded sensitive data. This appears to stem from improper access controls on certain endpoints or functionality that exposes system information or sensitive data to unauthorized users.

MitigationUpdate to a patched version of weMail if available, or implement access controls/authorization checks on all endpoints that return sensitive data. If no patch exists, restrict access to sensitive functionality via authentication requirements or firewall rules.

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
WemailWordPress extension
Affected:< 1.14.14

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate weMail plugin installation
    Check the WordPress plugins directory at wp-content/plugins/wemail/ for the plugin folder, or view the installed plugins list via WordPress admin under Plugins > Installed Plugins
    Affected if The weMail plugin folder exists and the plugin is active in WordPress
  2. Identify installed weMail version
    Open the main plugin file (typically weMail.php) in the weMail plugin folder and locate the version header comment (e.g., 'Version: 1.14.x') or check the plugin metadata via WordPress admin plugins page
    Affected if The reported version is below 1.14.14 (e.g., 1.14.13, 1.14.12, etc.)
  3. Map plugin endpoints that may expose data
    Review the plugin source files in wp-content/plugins/wemail/ for REST API routes, AJAX handlers, or callback functions that process requests. Look for files containing 'register_rest_route', 'add_action' hooks, or endpoint definitions that handle sensitive data retrieval
    Affected if The plugin contains custom endpoints or AJAX handlers that process data requests
  4. Test endpoint accessibility without authentication
    Using a tool like curl or a browser, attempt to access the identified weMail endpoints without providing authentication credentials (cookies or login tokens). For example: curl -v https://your-site.com/wp-json/wemail/v1/endpoint (replace with actual endpoint paths found in the code)
    Affected if The endpoints return sensitive data or system information without requiring authentication (HTTP 200 responses with data instead of 401/403)

You are affected if weMail plugin version is below 1.14.14 AND the plugin exposes sensitive endpoints that are accessible to unauthenticated users.

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
Upgrade available Upgrade to 1.14.14 or later
Fixed in 1.14.14
Interim mitigation

Update to a patched version of weMail if available, or implement access controls/authorization checks on all endpoints that return sensitive data. If no patch exists, restrict access to sensitive functionality via authentication requirements or firewall rules.

Recommended fix High confidence

wemail 1.14.14 or later

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to WordPress dashboard > Plugins > wemail
  3. 3. If an update is available, click 'Update Now' to upgrade to version 1.14.14 or later
  4. 4. Alternatively, download wemail version 1.14.14 or later from the WordPress plugin repository or weDevs and upload it manually via Plugins > Add New > Upload Plugin
  5. 5. After updating, verify the plugin version shows 1.14.14 or higher in the Plugins list

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

Fix this in Wemail Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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