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

CVE-2026-8895

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-09
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 kk blog card plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'blog-card' shortcode in all versions up to, and including, 1.3. This is due to insufficient input sanitization and output escaping on the shortcode's 'href' and 'type' attributes, which are concatenated directly into HTML attribute contexts in the shortcode callback registered in kk-blog-card-shortcode.php. 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 kk blog card WordPress plugin fails to sanitize and escape the 'href' and 'type' attributes in its [blog-card] shortcode, allowing authenticated users with contributor-level access to inject malicious JavaScript into pages. The unsanitized values are directly concatenated into HTML attribute contexts in kk-blog-card-shortcode.php, causing stored XSS that executes when other users view injected pages.

MitigationUpdate to a patched version of the plugin that implements proper input sanitization (e.g., esc_url() for href, sanitize_text_field() for type) and output escaping (e.g., esc_attr()) on shortcode attributes. Until a patch is available, restrict contributor-level user permissions and audit existing pages for injected shortcodes.

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. Locate the kk blog card plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'kk-blog-card' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'KK Blog Card' or 'kk-blog-card'.
    Affected if The plugin is found installed on the WordPress site.
  2. Determine the installed plugin version
    In WordPress admin, click on the plugin to view its details and read the version number. Alternatively, open the main plugin PHP file (often named kk-blog-card.php or similar in the plugin folder) and look for a 'Version:' comment in the file header.
    Affected if The version number is 1.3 or lower (the vulnerability exists in versions up to 1.3).
  3. Identify if the blog-card shortcode is in use
    Search WordPress database posts table for occurrences of the string '[blog-card' using phpMyAdmin or WP-CLI: wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%[blog-card%'" (adjust wp_ prefix if different).
    Affected if Any posts or pages contain the [blog-card] shortcode with user-supplied href or type attributes.
  4. Inspect the shortcode handler source code
    Open the file kk-blog-card-shortcode.php in the plugin directory and locate the shortcode callback function. Examine how the 'href' and 'type' attributes are handled - look for whether sanitize_url, esc_attr, or similar escaping functions are applied before outputting to HTML.
    Affected if The code directly concatenates shortcode attributes into HTML without sanitization (no sanitize_url, esc_url, or esc_attr calls found for the href and type attributes).

A site is affected if the kk-blog-card plugin version 1.3 or lower is installed AND the blog-card shortcode is being used with unsanitized href or type parameters in content.

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

Update to a patched version of the plugin that implements proper input sanitization (e.g., esc_url() for href, sanitize_text_field() for type) and output escaping (e.g., esc_attr()) on shortcode attributes. Until a patch is available, restrict contributor-level user permissions and audit existing pages for injected shortcodes.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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