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

CVE-2026-3513

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
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 TableOn – WordPress Posts Table Filterable plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'tableon_button' shortcode in all versions up to and including 1.0.4.4. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes such as 'class', 'help_link', 'popup_title', and 'help_title'. The do_shortcode_button() function extracts these attributes without sanitization and passes them to TABLEON_HELPER::draw_html_item(), which concatenates attribute values into HTML using single quotes without escaping (line 29: $item .= " {$key}='{$value}'"). 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 TableOn WordPress plugin fails to sanitize shortcode attributes ('class', 'help_link', 'popup_title', 'help_title') before embedding them into HTML. The do_shortcode_button() function passes unsanitized values to TABLEON_HELPER::draw_html_item(), which concatenates attributes directly into HTML tags using single quotes without escaping (line 29: $item .= " {$key}='{$value}'"). This allows authenticated users with Contributor+ access to inject malicious JavaScript via the tableon_button shortcode.

MitigationUpdate to the latest version of TableOn plugin which includes proper input sanitization using WordPress escaping functions (esc_attr()) for all shortcode attributes before HTML output.

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. Verify TableOn plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'TableOn' or check the plugins directory for tableon folder. Note the installed version number.
    Affected if TableOn plugin is installed and the installed version is lower than the patched version (or unknown)
  2. Identify the installed version of TableOn
    Check the plugin header in wp-content/plugins/tableon/tableon.php for 'Version:' line, or view the plugin version in the WordPress plugins list.
    Affected if The installed version is older than the patched version or cannot be determined
  3. Search for usage of the vulnerable tableon_button shortcode
    Use WordPress database query or plugin to search post content for '[tableon_button' shortcode: SELECT * FROM wp_posts WHERE post_content LIKE '%[tableon_button%' AND post_status != 'trash';
    Affected if Any posts/pages contain the tableon_button shortcode with user-controlled attributes
  4. Inspect shortcode attributes for potential XSS payloads
    Examine posts containing tableon_button shortcode. Look for attributes like class, help_link, popup_title, help_title that contain quotes, script tags, or javascript: URLs.
    Affected if The shortcode contains unsanitized-looking attribute values (especially with quotes, angle brackets, or javascript: prefixes)
  5. Review Contributor-level user accounts
    In WordPress admin, go to Users > All Users and filter by 'Contributor' role, or query: SELECT * FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%';
    Affected if There are Contributor-level users who could potentially author content with the malicious shortcode

A user is affected if TableOn plugin is installed with an unpatched version AND the tableon_button shortcode is in use AND contributors have access to create or edit content.

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 the latest version of TableOn plugin which includes proper input sanitization using WordPress escaping functions (esc_attr()) for all shortcode attributes before HTML output.

Recommended fix Moderate confidence

TableOn plugin version 1.0.4.5 or later (check WordPress plugin repository for latest release)

  1. 1. Log in to the WordPress admin dashboard with Administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the TableOn – WordPress Posts Table Filterable plugin
  4. 4. Check the current installed version in the plugin list
  5. 5. If the installed version is 1.0.4.4 or lower, update the plugin to the latest available version
  6. 6. Verify the update completed successfully
  7. 7. Test the tableon_button shortcode functionality to ensure the update did not break legitimate features

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-3513 — 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-3513 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