CVE-2026-8846
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 · uneditedThe Tuxquote plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'TUXQUOTE' shortcode in versions up to, and including, 1.3. This is due to insufficient input sanitization and output escaping on user supplied attributes ('title', 'align', and 'width') in the tuxquote_build_format() function, which are concatenated into the rendered HTML without being passed through esc_attr() or esc_html(). 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 confidenceThe Tuxquote WordPress plugin up to version 1.3 contains a stored XSS vulnerability in the tuxquote_build_format() function. User-supplied attributes (title, align, width) from the TUXQUOTE shortcode are concatenated directly into HTML output without sanitization via esc_attr() or esc_html(), allowing authenticated Contributors+ to inject arbitrary JavaScript.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Tuxquote plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Tuxquote'. Note the installed version number.Affected if Tuxquote plugin is installed and version is 1.3 or lower
-
Locate the vulnerable functionIn the plugin directory, open the main plugin file and search for the function tuxquote_build_format(). This function handles the TUXQUOTE shortcode output.Affected if The function exists and processes shortcode attributes without esc_attr() or esc_html()
-
Verify missing sanitization on shortcode attributesInspect the tuxquote_build_format() function code. Look for the variables $title, $align, and $width being concatenated directly into HTML output strings.Affected if These attributes are concatenated into HTML without passing through esc_attr() or esc_html() sanitization functions
-
Check for active use of TUXQUOTE shortcodeSearch WordPress database or content files for occurrences of [tuxquote] shortcode in posts, pages, or custom post types.Affected if The TUXQUOTE shortcode is present in any published content and the plugin version is 1.3 or lower
A user is affected if the Tuxquote plugin version is 1.3 or lower AND the tuxquote_build_format() function lacks esc_attr()/esc_html() sanitization on the title, align, or width attributes, AND the TUXQUOTE shortcode is in use.
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 dataUpdate the Tuxquote plugin to a version beyond 1.3 that properly escapes all shortcode attributes using esc_attr() for HTML attributes and esc_html() for text content, or apply custom code fixes to add proper escaping in tuxquote_build_format().
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8846 — 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-8846 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