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

CVE-2026-6237

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Quick Table plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'style' attribute of the 'qtbl' shortcode in all versions up to, and including, 1.0.0 due to insufficient input sanitization and output escaping on user supplied attributes. 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 confidence

The Quick Table WordPress plugin <= 1.0.0 has a stored XSS vulnerability in the 'qtbl' shortcode's 'style' attribute. Authenticated users with contributor-level access can inject arbitrary JavaScript through unsanitized input that gets stored in the database and executed when other users access affected pages, due to insufficient input sanitization and output escaping.

MitigationUpdate to a patched version of the Quick Table plugin that properly sanitizes the 'style' attribute and implements output escaping. Until patched, limit contributor-level user permissions or temporarily disable the plugin.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Quick Table plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Quick Table' in the list. Check if it is activated.
    Affected if Quick Table plugin is installed and active with version 1.0.0 or lower
  2. Verify the plugin version
    Click on the plugin name or 'View Details' link to display the version number. Compare it to the affected range: any version <= 1.0.0.
    Affected if Installed version is 1.0.0 or lower (no patched version is in use)
  3. Identify pages using the qtbl shortcode
    Search the WordPress database via phpMyAdmin or WP-CLI for posts containing the '[qtbl' shortcode string. Example SQL: SELECT * FROM wp_posts WHERE post_content LIKE '%[qtbl%' AND post_status='publish';
    Affected if Any published content contains the [qtbl] shortcode with a style attribute
  4. Inspect stored shortcode attributes for malicious content
    Examine the post_content in the database for entries containing [qtbl. Look specifically at the style= parameter for unsanitized values such as javascript:, onload=, or unusual HTML/JS like <script> tags, event handlers, or encoded payloads.
    Affected if The style attribute contains unexpected characters like quotes, angle brackets, or javascript: protocol handlers
  5. Check for contributor-level user accounts
    Go to WordPress admin > Users and review user roles. Identify any accounts with 'Contributor' role.
    Affected if There are one or more contributor-level users who could potentially inject malicious content

You are affected if the Quick Table plugin version is 1.0.0 or lower, the qtbl shortcode is in use on your site, and contributor-level users exist (or any authenticated users have access to create/edit content with shortcodes).

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 to a patched version of the Quick Table plugin that properly sanitizes the 'style' attribute and implements output escaping. Until patched, limit contributor-level user permissions or temporarily disable the plugin.

Recommended fix Moderate confidence

Latest version beyond 1.0.0 (check WordPress plugin repository for the patched release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Quick Table plugin
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, update to the latest version that includes the security fix
  6. 6. If no update is available through the WordPress admin, check the WordPress plugin repository at plugins.trac.wordpress.org for the latest patched version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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