CVE-2026-27068
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Ryan Howard Website LLMs.txt website-llms-txt allows Reflected XSS.This issue affects Website LLMs.txt: from n/a through <= 8.2.6.
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 confidenceThe website-llms-txt WordPress plugin through version 8.2.6 contains a reflected cross-site scripting (XSS) vulnerability where user-supplied input is not properly sanitized or escaped before being rendered in web pages. An attacker can craft malicious URLs containing JavaScript payloads that execute in victim browsers when triggered.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Check if the website-llms-txt plugin is installedNavigate to WordPress admin > Plugins and look for 'website-llms-txt' in the installed plugins list, or check the /wp-content/plugins/ directory for a folder named 'website-llms-txt'Affected if the plugin folder exists in the WordPress plugins directory
-
Determine the installed plugin versionIn WordPress admin > Plugins, click on the plugin name to view the version details, or open the main plugin file (e.g., website-llms-txt.php) and look for the 'Version:' header in the plugin commentsAffected if the version number displayed is 8.2.6 or lower
-
Confirm the plugin is activeIn WordPress admin > Plugins, verify that the website-llms-txt plugin shows as 'Active' under its statusAffected if the plugin shows an 'Active' status (inactive plugins do not execute the vulnerable code)
-
Identify vulnerable URL parameter reflectionIf the plugin is active and version is <= 8.2.6, manually test URL parameters by visiting pages where the plugin loads (such as /?llms_txt=example or similar endpoints) and inspect the page source to see if input is reflected without encodingAffected if URL parameters from the plugin are rendered in HTML output without proper escaping (visible by viewing page source)
A user is affected if the website-llms-txt plugin is installed, is active, and runs version 8.2.6 or lower where unsanitized URL parameters are reflected in the HTML output.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper output encoding/escaping for all user inputs reflected in HTML pages, and consider adding Content-Security-Policy headers. Validate and sanitize all URL parameters before use.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27068 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27068 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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