dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8089

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
The weMail: Email Marketing, Email Automation, Newsletters, Subscribers & Email Optins for WooCommerce WordPress plugin before 2.1.3 does not properly escape a user-supplied parameter before reflecting it into an HTML attribute on a non-nonce-protected AJAX response, allowing unauthenticated attackers to deliver Reflected Cross-Site Scripting against any authenticated user (including administrators) via a crafted URL.

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 before version 2.1.3 contains a reflected XSS vulnerability where a user-supplied parameter is not properly escaped before being reflected into an HTML attribute. The AJAX endpoint lacking nonce protection allows unauthenticated attackers to craft malicious URLs that, when clicked by an authenticated user (including administrators), execute arbitrary JavaScript in the victim's browser.

MitigationUpdate the weMail plugin to version 2.1.3 or later to obtain the patched version that properly escapes user input and implements nonce validation on AJAX endpoints.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Identify if weMail plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'weMail' or check the plugins directory for the welmail folder. Alternatively, check for weMail-related files in /wp-content/plugins/
    Affected if weMail plugin is not found in the WordPress installation
  2. Determine installed weMail version
    In WordPress admin, go to Plugins > Installed Plugins > weMail and view the version number displayed, or check the main plugin file header in /wp-content/plugins/welmail/welmail.php for the Version tag
    Affected if Version is present but less than 2.1.3 (for example, 2.1.2, 2.1.1, 2.0.x, etc.)
  3. Verify AJAX endpoint accessibility
    Identify the AJAX endpoint URL used by weMail (typically /wp-admin/admin-ajax.php with a weMail-specific action parameter). Check if the endpoint responds to requests without requiring nonce validation by inspecting the plugin code for admin-ajax.php hooks and their callback functions
    Affected if The weMail AJAX endpoint is active and accessible without proper nonce verification on the relevant action
  4. Check for reflected parameter handling
    Examine the plugin code for the AJAX handler that processes user-supplied GET or POST parameters. Look for instances where request parameters are directly output into HTML without sanitization (such as using echo or print with $_GET, $_POST, or $_REQUEST values in HTML attribute contexts)
    Affected if User-supplied parameters from requests are reflected into HTML output without proper escaping or sanitization

A user is affected if weMail plugin version is below 2.1.3 and the AJAX endpoint handles user input in a way that reflects unsanitized parameters into HTML attributes.

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.1.3 or later to obtain the patched version that properly escapes user input and implements nonce validation on AJAX endpoints.

Recommended fix High confidence

weMail plugin version 2.1.3 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the weMail plugin in the list
  4. Check if an update to version 2.1.3 or later is available
  5. If an update is available, click 'Update Now' to install the fixed version
  6. If no automatic update is available, manually download version 2.1.3 or later from the WordPress plugin repository
  7. Deactivate and delete the current weMail plugin, then upload and install the updated version
  8. Verify the plugin is running at version 2.1.3 or later after update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing2.0 h
  • Review / QA1.0 h
4.5 hours of engineering $770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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