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

CVE-2026-3619

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-21
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 Sheets2Table plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'titles' shortcode attribute in the [sheets2table-render-table] shortcode in all versions up to and including 0.4.1. This is due to insufficient input sanitization and output escaping. Specifically, the 'titles' attribute value from the shortcode is passed through S2T_Functions::trim_array_values() (which only trims whitespace) and then echoed directly into HTML via `echo $header` inside a <th> tag in the display_table_header() function without any escaping such as 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 confidence

The Sheets2Table WordPress plugin up to version 0.4.1 suffers from a stored XSS vulnerability in the [sheets2table-render-table] shortcode. The 'titles' attribute is processed by S2T_Functions::trim_array_values() which only removes whitespace, then echoed unescaped via `echo $header` inside <th> tags in display_table_header(), allowing injection of arbitrary JavaScript.

MitigationUpdate to a patched version if available; otherwise, add esc_html() escaping around the $header variable output in display_table_header() and implement input validation using sanitize_text_field() on the 'titles' attribute before processing.

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 Sheets2Table plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for Sheets2Table, or check the plugin directory /wp-content/plugins/ for a sheets2table folder
    Affected if The plugin is installed and active
  2. Determine installed plugin version
    In WordPress admin plugins list, click on the plugin to view details, or read the main plugin PHP file header for the Version field
    Affected if Version is 0.4.1 or lower
  3. Find usage of the vulnerable shortcode
    Search the WordPress database: SELECT * FROM wp_posts WHERE post_content LIKE '%[sheets2table-render-table%' AND post_status IN ('publish','draft','pending','private')
    Affected if The shortcode [sheets2table-render-table] is present in any post or page content
  4. Check for titles attribute usage
    Query posts containing the shortcode and examine if the titles attribute is present: SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%[sheets2table-render-table%titles=%'
    Affected if The titles attribute is used within the shortcode
  5. Inspect shortcode output for unescaped content
    View the source of a published page using the shortcode with a titles attribute; look at the table header <th> elements to see if content appears unescaped (e.g., <th>Test</th> vs raw HTML present)
    Affected if The table header output contains unescaped HTML or JavaScript in <th> tags

You are affected if Sheets2Table version 0.4.1 or lower is installed AND the [sheets2table-render-table] shortcode with a titles attribute is used in any published 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 a patched version if available; otherwise, add esc_html() escaping around the $header variable output in display_table_header() and implement input validation using sanitize_text_field() on the 'titles' attribute before processing.

Recommended fix Moderate confidence

Latest version of Sheets2Table plugin (greater than 0.4.1)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the Sheets2Table plugin
  4. Check if an update is available and update to the latest version
  5. If no update is available through WordPress, manually download the latest version from the WordPress plugin repository and reinstall

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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