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

CVE-2026-8865

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 Avalon23 Products Filter for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'avalon23_qr' shortcode in all versions up to, and including, 1.1.6. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes (notably 'title' and 'fixed_link') which are concatenated directly into single-quoted HTML attributes by the AVALON23_HELPER::draw_html_item() helper without esc_attr() or any other encoding. 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 Avalon23 Products Filter for WooCommerce plugin has a stored XSS vulnerability in versions up to 1.1.6. The 'avalon23_qr' shortcode handler directly concatenates user-supplied 'title' and 'fixed_link' attributes into single-quoted HTML attributes without esc_attr() or any output escaping, allowing authenticated Contributors+ to inject malicious JavaScript that executes when users view affected pages.

MitigationUpdate the plugin to version 1.1.7 or later which applies proper escaping via esc_attr(); alternatively, disable the vulnerable shortcode until patched.

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. Determine the installed version of the Avalon23 Products Filter for WooCommerce plugin
    Locate the main plugin file (commonly named avalon23-products-filter.php or similar) in wp-content/plugins/ and read the 'Version:' header at the top of the file.
    Affected if The version listed is 1.1.6 or lower.
  2. Find pages or posts that use the vulnerable shortcode
    Query the WordPress database (e.g., SELECT * FROM wp_posts WHERE post_content LIKE '%[avalon23_qr%') or use the WP admin search to list all posts containing the string '[avalon23_qr'.
    Affected if Any published post, page, or custom post type contains the [avalon23_qr] shortcode.
  3. Identify if the shortcode is used with the 'title' or 'fixed_link' attributes
    Search the same post content for patterns like '[avalon23_qr title="..."' or '[avalon23_qr fixed_link="..."', or inspect the shortcode attributes in the plugin's code that handles the shortcode.
    Affected if The shortcode appears with a 'title' or 'fixed_link' attribute in any post.
  4. Verify the shortcode handler lacks output escaping
    Open the file that defines the 'avalon23_qr' shortcode callback (often in the main plugin file or a separate includes file). Locate the code that outputs the 'title' and 'fixed_link' values into HTML attributes and confirm they are not wrapped with esc_attr() or other escaping functions.
    Affected if The code directly concatenates the attribute values into HTML without esc_attr() or equivalent sanitization.

If the plugin version is 1.1.6 or lower and any page uses the [avalon23_qr] shortcode with the 'title' or 'fixed_link' attribute, the site is vulnerable to stored XSS.

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

Update the plugin to version 1.1.7 or later which applies proper escaping via esc_attr(); alternatively, disable the vulnerable shortcode until patched.

Recommended fix Moderate confidence

Version 1.1.7 or later (update to latest available version in the WordPress plugin repository)

  1. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  2. Locate the Avalon23 Products Filter for WooCommerce plugin
  3. Check the current installed version (should be 1.1.6 or earlier)
  4. Update the plugin to the latest available version from the WordPress plugin repository
  5. Verify the update was successful by confirming the new version number
  6. Test that the avalon23_qr shortcode with title and fixed_link attributes now properly escapes output using esc_attr() or equivalent encoding

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
  • 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-8865 — 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-8865 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