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

CVE-2026-8894

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
The iWR Tooltip plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `iwrtooltip` shortcode in versions up to, and including, 1.0. This is due to insufficient input sanitization and output escaping on user supplied attributes in the iwr_tooltip() shortcode handler — the `title` attribute is concatenated directly into an HTML attribute without esc_attr() or any other escaping. 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 iWR Tooltip WordPress plugin has a stored XSS vulnerability in versions up to 1.0. The `iwrtooltip` shortcode handler does not sanitize or escape the `title` attribute before concatenating it directly into an HTML attribute, allowing injection of arbitrary JavaScript that executes when users view pages containing the malicious shortcode.

MitigationReplace direct attribute concatenation with proper escaping using esc_attr() on the title parameter in the shortcode handler, and implement input validation. If no patched version exists, contact the plugin developer or consider removing the plugin until fixed.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm iWR Tooltip plugin is installed
    Navigate to WordPress admin Plugins page and check if 'iWR Tooltip' appears in the installed plugins list, or inspect the wp-content/plugins directory for an iwr-tooltip folder
    Affected if The plugin appears in the installed plugins list or directory
  2. Check the installed plugin version
    In WordPress admin, click on the plugin to view its details and locate the version number, or open the main plugin file (usually iwr-tooltip.php) and look for the Version header comment
    Affected if The version is 1.0 or any version up to and including 1.0 (no patched version is indicated)
  3. Search for usage of the iwrtooltip shortcode
    Search the WordPress database posts table for occurrences of '[iwrtooltip' using phpMyAdmin or WP-CLI: wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%[iwrtooltip%'"
    Affected if Any posts, pages, or custom post types contain the [iwrtooltip] shortcode
  4. Inspect the shortcode handler code
    Locate the shortcode handler function in the plugin file (typically in the main plugin PHP file), look for the handler that processes the 'title' attribute, and verify if esc_attr() or similar escaping is used before outputting the title into HTML
    Affected if The code directly concatenates the title attribute into an HTML attribute without sanitization (no esc_html, esc_attr, or similar escaping functions)
  5. Check for malicious shortcode variations in content
    Review pages containing the [iwrtooltip] shortcode and inspect the rendered HTML in the browser developer tools, looking for unescaped characters in the title attribute
    Affected if The rendered title attribute contains unescaped quotes, angle brackets, or JavaScript event handlers

A user is affected if the iWR Tooltip plugin version 1.0 or lower is installed AND the [iwrtooltip] shortcode is used in any content with a title attribute that is not properly escaped in the output HTML.

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

Replace direct attribute concatenation with proper escaping using esc_attr() on the title parameter in the shortcode handler, and implement input validation. If no patched version exists, contact the plugin developer or consider removing the plugin until fixed.

Recommended fix Moderate confidence

Version 1.1 or later (after 1.0)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the iWR Tooltip plugin
  4. Check if a newer version is available and upgrade to the latest fixed version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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