CVE-2026-6712
Stored XSS in Website LLMs.txt WordPress Plugin Allows Admin Script Injection
Publication date: 2026-04-21
Last updated on: 2026-04-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | website_llms | to 8.2.6 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that your WordPress installation is not running a multi-site setup or that the unfiltered_html setting is enabled if applicable.
Update the Website LLMs.txt plugin to a version later than 8.2.6 where the vulnerability has been fixed.
Restrict administrator-level permissions carefully, as only authenticated users with such permissions can exploit this vulnerability.
Can you explain this vulnerability to me?
The Website LLMs.txt plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to and including 8.2.6. This vulnerability arises because the plugin does not properly sanitize input or escape output in the admin settings.
Authenticated users with administrator-level permissions or higher can exploit this flaw to inject arbitrary web scripts into pages. These scripts execute whenever any user accesses the affected page.
This vulnerability specifically affects multi-site WordPress installations and installations where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with administrator privileges to inject malicious scripts that execute in the browsers of users visiting the affected pages.
Such script execution can lead to theft of user credentials, session hijacking, defacement of the website, or distribution of malware.
Because the vulnerability requires high privileges and affects multi-site or restricted HTML installations, the risk is somewhat limited but still significant in those environments.