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

CVE-2026-6711

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Website LLMs.txt plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'tab' parameter in all versions up to, and including, 8.2.6. This is due to the use of filter_input() without a sanitization filter and insufficient output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick an administrator into performing an action such as clicking on a link.

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 Website LLMs.txt WordPress plugin uses filter_input() to retrieve the 'tab' parameter without applying a sanitization filter, and the output is not properly escaped when rendered. This allows unauthenticated attackers to inject arbitrary JavaScript via a malicious URL that executes in an administrator's browser when they click the link (reflected XSS).

MitigationUpdate the plugin to a patched version once available. In the meantime, warn administrators to avoid clicking untrusted links to mitigate the social engineering vector.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Website LLMs.txt plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Website LLMs.txt' or check the plugin files in wp-content/plugins/llms-txt/ directory
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    Check the plugin main file (e.g., llms-txt.php) for the version header comment, or view the plugin details in the WordPress plugins admin page
    Affected if The version is unknown or within a range that lacks the fix for CVE-2026-6711 (the plugin processes the 'tab' parameter without sanitization)
  3. Inspect the tab parameter handling code
    Locate the plugin PHP file that processes the 'tab' query parameter (search for filter_input(INPUT_GET, 'tab') or $_GET['tab']) and verify whether the value is sanitized (e.g., via sanitize_text_field, esc_html) before output
    Affected if The code uses filter_input() or $_GET['tab'] without applying a sanitization function before echoing the value
  4. Check if output escaping is applied when rendering the tab value
    Search the plugin code for where the tab parameter value is output (echo or print statements involving the tab variable) and verify that proper escaping functions (esc_html, esc_attr) are used
    Affected if The tab value is echoed directly or without escaping functions, allowing injected JavaScript to execute
  5. Test the reflected XSS via a crafted URL
    With administrator privileges, attempt to access a URL like yoursite.com/wp-admin/admin.php?page=llms-txt&tab=<img+src=x+onerror=alert(1)> and observe if the alert executes or inspect the page source for the unescaped payload
    Affected if The injected script tag appears unescaped in the HTML output and executes in the browser

A user is affected if the Website LLMs.txt plugin is installed and processes the 'tab' parameter without sanitizing or escaping the output, allowing reflected XSS to trigger when an administrator clicks a malicious link.

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 a patched version once available. In the meantime, warn administrators to avoid clicking untrusted links to mitigate the social engineering vector.

Recommended fix Moderate confidence

Latest version higher than 8.2.6 (check WordPress plugin repository for current stable release)

  1. 1. Check the WordPress plugin repository for the Website LLMs.txt plugin to identify the latest available version
  2. 2. Verify that the latest version is higher than 8.2.6
  3. 3. Update the plugin to the latest version via WordPress admin dashboard or via wp-cli: wp plugin update llms-txt
  4. 4. Confirm the update completed successfully
  5. 5. Test the 'tab' parameter functionality to ensure the fix does not break legitimate functionality

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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