← Back to results
Vulnerability record · public intelligence
CVE-2026-75980
MEDIUM

BetterDocs <= 4.8.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Heading 'id' Attribute in Post Content

Published Sep 1, 2026 · Updated Oct 23, 2026

Severity · CVSSMEDIUM · 6.4
Known exploitationNot listed
EPSS / likelihood0.35%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

BetterDocs <= 4.8.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Heading 'id' Attribute in Post Content

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

The BetterDocs – AI Documentation, Knowledge Base, Docs, Wikis, FAQ with Chatbot plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Heading 'id' Attribute in Post Content in all versions up to, and including, 4.8.1 due to insufficient input sanitization and output 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. The exploit survives wp_kses_post because entity-encoded quotes in a heading id attribute are treated as a single legitimate attribute value at save time; the dangerous payload only materialises after process_content_for_toc() calls html_entity_decode() on the stored content and the broken id is extracted by a lazy regex before being echoed unescaped into the Table of Contents output.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. www.wordfence.com ↗
  2. plugins.trac.wordpress.org ↗
  3. plugins.trac.wordpress.org ↗
  4. plugins.trac.wordpress.org ↗
  5. plugins.trac.wordpress.org ↗
  6. plugins.trac.wordpress.org ↗

Record history

Published Sep 1, 2026 · Last refreshed Oct 23, 2026