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

CVE-2026-8896

MEDIUM · 6.4 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 →
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 MIR blocks and shortcodes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title' attribute (and other attributes such as 'ready_animation_text') of the 'msc_stats' shortcode in versions up to, and including, 1.0.0. This is due to insufficient input sanitization and output escaping on user supplied shortcode attributes inside the msc_stats() rendering function. 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 MIR blocks and shortcodes WordPress plugin up to version 1.0.0 suffers from a stored XSS vulnerability in the msc_stats shortcode. Authenticated attackers with contributor-level access can inject malicious JavaScript via unsanitized shortcode attributes (title, ready_animation_text, etc.) that persist in page content and execute when users view affected pages.

MitigationApply input sanitization (sanitize_text_field, esc_attr) to all shortcode attributes before output and ensure proper output escaping (esc_html, esc_attr) in the msc_stats() rendering function. Update to any version beyond 1.0.0 if available.

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. Verify MIR blocks and shortcodes plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'MIR blocks and shortcodes' in the list. Note the version number displayed next to the plugin name.
    Affected if Plugin is present and version is 1.0.0 or lower (no version after 1.0.0 is indicated as fixed)
  2. Identify usage of the msc_stats shortcode
    Search your WordPress database or use a plugin to find all posts/pages containing the [msc_stats] shortcode. Check pages, posts, and custom post types.
    Affected if The shortcode [msc_stats] appears in any published content
  3. Inspect shortcode attributes for lack of sanitization
    Examine the content where [msc_stats] is used. Look for attributes such as 'title', 'ready_animation_text', or any other attributes passed to the shortcode. Check if these values contain special characters like < > " ' that could indicate injected scripts.
    Affected if Any instance of msc_stats shortcode contains unsanitized user-supplied attributes (especially title, ready_animation_text) that could contain script tags or event handlers
  4. Confirm vulnerability context requires authenticated access
    Verify that contributor-level or higher user accounts exist in the WordPress installation, as the attack requires authenticated contributor-level access to inject the malicious shortcode.
    Affected if Contributor-level or higher user accounts exist and the plugin version is <= 1.0.0 with msc_stats shortcode in use

The environment is affected if the MIR blocks and shortcodes plugin version is 1.0.0 or lower AND the msc_stats shortcode with any attributes is present in published content, allowing stored XSS injection.

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 input sanitization (sanitize_text_field, esc_attr) to all shortcode attributes before output and ensure proper output escaping (esc_html, esc_attr) in the msc_stats() rendering function. Update to any version beyond 1.0.0 if available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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