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

CVE-2026-8886

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 hk_shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title-plane' shortcode in versions up to, and including, 1.0. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes in the huankong_post_short_title_plane() function, where the 'title' attribute is concatenated directly into HTML output without any 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 hk_shortcode WordPress plugin is vulnerable to Stored Cross-Site Scripting via the 'title-plane' shortcode. The 'title' attribute is directly concatenated into HTML output in the huankong_post_short_title_plane() function without sanitization or escaping, allowing authenticated contributors+ to inject arbitrary JavaScript.

MitigationApply proper output escaping (esc_html() or esc_attr()) to the 'title' attribute in the huankong_post_short_title_plane() function before HTML output, and implement input validation on shortcode attributes.

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 hk_shortcode plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'hk_shortcode' or 'Huankong Shortcode' in the list. Alternatively, check the wp-content/plugins directory for a folder named 'hk-shortcode' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In the Plugins list in WordPress admin, click on the plugin name to view details, or check the plugin's main PHP file header for the 'Version' comment. Compare this to any known affected versions.
    Affected if The version is within an affected range (if such ranges become known)
  3. Locate the vulnerable function in source code
    Access the plugin files via file manager or FTP, and open the main plugin PHP file. Search for the function 'huankong_post_short_title_plane' and examine how it handles the 'title' attribute.
    Affected if The function exists and directly outputs the 'title' attribute without esc_html() or esc_attr() wrapping
  4. Check if title-plane shortcode is in use
    Search WordPress post content (in wp_posts table or via admin Posts list) for occurrences of the shortcode [title-plane] or [title-plane title=...] in published content.
    Affected if The shortcode is present in any published post or page content
  5. Verify contributor+ user access exists
    In WordPress admin, go to Users > All Users and review the role assigned to each user. Contributor, Author, Editor, and Administrator roles all have privileges that can trigger the vulnerable shortcode.
    Affected if Any user account with Contributor role or higher exists on the site

The environment is affected if the hk_shortcode plugin is installed, the vulnerable huankong_post_short_title_plane function is present without proper escaping, and the title-plane shortcode is in use by users with contributor+ access.

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 proper output escaping (esc_html() or esc_attr()) to the 'title' attribute in the huankong_post_short_title_plane() function before HTML output, and implement input validation on shortcode attributes.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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