dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2025-14348

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
The weMail - Email Marketing, Lead Generation, Optin Forms, Email Newsletters, A/B Testing, and Automation plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.0.7. This is due to the plugin's REST API trusting the `x-wemail-user` HTTP header to identify users without verifying the request originates from an authenticated WordPress session. This makes it possible for unauthenticated attackers who know or can guess an admin email (easily enumerable via `/wp-json/wp/v2/users`) to impersonate that user and access the CSV subscriber endpoints, potentially exfiltrating subscriber PII (emails, names, phone numbers) from imported CSV files.

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

The weMail WordPress plugin versions up to 2.0.7 have an authorization bypass vulnerability in its REST API. The plugin trusts the `x-wemail-user` HTTP header to identify users without verifying the request originates from an authenticated WordPress session, allowing unauthenticated attackers to impersonate administrators by setting this header to a known admin email address and access CSV subscriber endpoints to exfiltrate PII.

MitigationUpdate the weMail plugin to version 2.0.8 or later, which should include proper authentication verification for the REST API endpoints. Until patched, consider restricting access to the `/wp-json/wp/v2/users` endpoint or temporarily disabling the plugin.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Confirm weMail plugin is installed
    Navigate to WordPress admin > Plugins and locate weMail, or check the filesystem at /wp-content/plugins/wemail/ and inspect the main plugin file for the version number
    Affected if weMail plugin version 2.0.7 or earlier is installed
  2. Verify plugin is active
    Check WordPress admin > Plugins for the active status of weMail, or query the database wp_options table for option_name containing 'active_plugins'
    Affected if weMail plugin is active and version is 2.0.7 or earlier
  3. Identify accessible REST API endpoints
    Probe the endpoint /wp-json/wemail/v1/subscribers/csv using a tool like curl or Burp Suite, sending a request without authentication
    Affected if The endpoint returns a valid CSV response or accepts the request without 401/403 authentication errors
  4. Test for vulnerable header processing
    Send a request to the CSV endpoint with an arbitrary x-wemail-user header set to a known admin email address (e.g., [email protected]) and observe if the response changes or succeeds
    Affected if Setting the x-wemail-user header to a valid admin email allows access to subscriber data without valid WordPress authentication

A user is affected if weMail plugin version 2.0.7 or earlier is active and the REST API endpoints at /wp-json/wemail/ are accessible without proper WordPress session authentication, particularly when the x-wemail-user header can be used to impersonate administrators.

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

Update the weMail plugin to version 2.0.8 or later, which should include proper authentication verification for the REST API endpoints. Until patched, consider restricting access to the `/wp-json/wp/v2/users` endpoint or temporarily disabling the plugin.

Recommended fix High confidence

weMail version 2.0.8 or later (latest stable release)

  1. 1. Update the weMail plugin to the latest available version from the WordPress plugin repository
  2. 2. Navigate to WordPress Admin > Plugins > weMail
  3. 3. If an update is available, click 'Update Now'
  4. 4. After updating, verify the REST API endpoints are properly secured by confirming the `x-wemail-user` header is no longer trusted without session verification
  5. 5. Optionally, restrict access to `/wp-json/wp/v2/users` endpoint via .htaccess or a security plugin to prevent user enumeration
Caveat None expected - this is a security patch fix

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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