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

CVE-2026-8866

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 jQuery googleslides plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'googleslides' shortcode in all versions up to, and including, 1.3. This is due to insufficient input sanitization and output escaping on user supplied attributes (userid, albumid, authkey, imgmax, maxresults, random, caption, albumlink, time, and fadespeed) in the googleslides_handler() function, which interpolates the attribute values directly into single-quoted HTML attributes without using esc_attr(). 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 WordPress googleslides plugin fails to escape shortcode attributes (userid, albumid, authkey, imgmax, maxresults, random, caption, albumlink, time, fadespeed) before rendering them into HTML, allowing authenticated attackers with contributor+ permissions to inject malicious scripts via the googleslides shortcode.

MitigationUpgrade to plugin version 1.4 or later which implements proper output escaping via esc_attr(); until then, restrict shortcode usage to trusted users only.

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. Check if googleslides plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'googleslides' or check the /wp-content/plugins/ directory for a googleslides folder
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In Plugins list, click on the plugin name to view details, or open the main plugin file (e.g., googleslides.php) and look for the Version header in the plugin comments
    Affected if Version is below 1.4 (the fixed version) or the version cannot be determined
  3. Verify shortcode is in use
    Search WordPress posts/pages/custom post types in the database (wp_posts table) for the shortcode [googleslides] or [googleslides userid=], or use a plugin like Search Regex to scan content
    Affected if Content contains the googleslides shortcode with any of these attributes: userid, albumid, authkey, imgmax, maxresults, random, caption, albumlink, time, fadespeed
  4. Check user role permissions
    Review WordPress user roles at Users > All Users; verify if contributor, author, editor, or administrator roles exist and have shortcode publishing capability
    Affected if Any user role below administrator (contributor, author, editor) can create or edit content containing shortcodes

If the googleslides plugin is installed with a version below 1.4 AND the shortcode is published on the site with untrusted user access, the environment is affected by this stored XSS vulnerability.

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

Upgrade to plugin version 1.4 or later which implements proper output escaping via esc_attr(); until then, restrict shortcode usage to trusted users only.

Recommended fix Moderate confidence

Version 1.4 or later

  1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. Locate the 'jQuery googleslides' plugin in the list
  3. Check if an update is available for the plugin
  4. If an update is available, update to the latest version (version 1.4 or higher)
  5. If no update is available through WordPress, download the latest version from the WordPress Plugin Repository at plugins.trac.wordpress.org and manually update
  6. After updating, verify that the plugin functions correctly on the site

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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