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

CVE-2026-10091

HIGH · 7.2 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/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
The Email JavaScript Cloak plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'email' shortcode in all versions up to, and including, 1.03 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Email JavaScript Cloak WordPress plugin versions up to 1.03 contains a stored XSS vulnerability in its 'email' shortcode due to missing input sanitization and output escaping on user-supplied attributes, allowing authenticated contributor+ users to inject malicious JavaScript that executes when visitors access affected pages.

MitigationUpdate the plugin to a patched version once available, or remove/uninstall the plugin if no update exists; scan existing content for injected scripts and remove any malicious payloads.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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. Check plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Email JavaScript Cloak' and read the version number displayed under the plugin name
    Affected if The displayed version is 1.03 or any version lower than 1.03 (the plugin displays up to 1.03 as vulnerable)
  2. Identify shortcode usage in content
    Search your WordPress database or use a plugin to find all posts/pages containing the shortcode [email] - check both classic editor content and Gutenberg blocks for occurrences
    Affected if The [email] shortcode is present in any published content on the site
  3. Inspect shortcode attributes for unsanitized input
    Examine the content where the [email] shortcode is used; look at how the 'email' attribute and any other attributes are populated - check if they contain raw user input without encoding or if they appear to contain script tags or event handlers like onload, onerror, or javascript:
    Affected if The shortcode attributes contain raw user-supplied email addresses or other data without sanitization, or if you see encoded HTML entities where plain text was expected
  4. Review contributor-level user accounts
    In WordPress admin, go to Users > All Users and identify any accounts with the Contributor role; also check any custom roles that have permissions equivalent to Contributor or above
    Affected if There are one or more contributor+ user accounts present on the site who could have authored content with the malicious shortcode
  5. Audit recent content edits by contributor users
    Review the revision history or activity logs for posts/pages created or edited by users with Contributor or Author roles; examine the raw content for any suspicious attribute values in [email] shortcodes
    Affected if Any content authored by contributor+ users contains the [email] shortcode with attribute values that include special characters, encoded scripts, or anything other than plain text email addresses

Your site is likely affected if the Email JavaScript Cloak plugin version is 1.03 or below AND the [email] shortcode is present in any content AND your site has contributor+ user accounts, as this combination allows authenticated attackers to inject persistent malicious scripts.

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 plugin to a patched version once available, or remove/uninstall the plugin if no update exists; scan existing content for injected scripts and remove any malicious payloads.

Recommended fix Moderate confidence

Latest version of Email JavaScript Cloak plugin (version > 1.03)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Email JavaScript Cloak' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update appears, manually download the latest version from the WordPress plugin repository and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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