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

CVE-2026-8701

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 GNTT Post Title Ticker plugin for WordPress is vulnerable to Stored Cross-Site Scripting in version 1.0 via the `title-ticker-slide`, `title-ticker-fade`, and `title-ticker-typing` shortcodes. This is due to insufficient input sanitization and output escaping on shortcode attributes (notably `border`, `width`, `height`, `header_background`, `header_text_color`, and `id`) within the `gntt_title_ticker_slide()`, `gntt_title_ticker_fade()`, and `gntt_title_ticker_typing()` functions. None of these attribute values are passed through `esc_attr()` or any other escaping function before being concatenated into HTML output. 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 GNTT Post Title Ticker WordPress plugin fails to sanitize shortcode attributes (`border`, `width`, `height`, `header_background`, `header_text_color`, `id`) before outputting them in HTML. Three shortcode handler functions (`gntt_title_ticker_slide`, `gntt_title_ticker_fade`, `gntt_title_ticker_typing`) directly concatenate unsanitized attribute values into HTML, allowing authenticated attackers with contributor-level access to inject malicious JavaScript that executes on page load.

MitigationApply `esc_attr()` to all shortcode attribute values before HTML output concatenation in the three affected functions, or use WordPress shortcode_atts() with proper escaping.

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 plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number for 'GNTT Post Title Ticker'.
    Affected if The installed version lacks a security patch for this vulnerability (verify against plugin changelog or security advisories).
  2. Identify shortcode usage
    Search WordPress content (posts, pages, custom post types) for the shortcodes [gntt_title_ticker_slide], [gntt_title_ticker_fade], or [gntt_title_ticker_typing].
    Affected if Any of these shortcodes are present in published content, as the vulnerability is only exploitable when the shortcode is rendered.
  3. Inspect code for sanitization
    Locate the plugin's main PHP file (typically in wp-content/plugins/gntt-post-title-ticker/) and find the functions gntt_title_ticker_slide, gntt_title_ticker_fade, and gntt_title_ticker_typing. Examine if the attributes (border, width, height, header_background, header_text_color, id) are sanitized with esc_attr() or equivalent before being output in HTML.
    Affected if The code directly concatenates these attributes into HTML without esc_attr() or similar escaping, indicating the vulnerability is present.

The environment is affected if the plugin is installed, the vulnerable shortcodes are used in content, and the plugin code does not sanitize the mentioned attributes with esc_attr().

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply `esc_attr()` to all shortcode attribute values before HTML output concatenation in the three affected functions, or use WordPress shortcode_atts() with proper escaping.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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