CVE-2026-3619
Received Received - Intake
Stored XSS in Sheets2Table WordPress Plugin via Shortcode Attribute

Publication date: 2026-03-21

Last updated on: 2026-03-21

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-21
Last Modified
2026-03-21
Generated
2026-05-07
AI Q&A
2026-03-21
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
tony_hetrick sheets2table to 0.4.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The Sheets2Table plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in the 'titles' shortcode attribute of the [sheets2table-render-table] shortcode in all versions up to 0.4.1.

This vulnerability occurs because the input provided in the 'titles' attribute is not properly sanitized or escaped before being output in the HTML. Specifically, the attribute value is only trimmed of whitespace but then echoed directly inside a table header (<th>) tag without escaping, allowing malicious scripts to be injected.

Authenticated users with Contributor-level access or higher can exploit this to inject arbitrary web scripts that execute whenever a user views the affected page.


How can this vulnerability impact me? :

This vulnerability can allow an attacker with Contributor-level access or above to inject malicious scripts into pages on your WordPress site.

When other users visit these pages, the injected scripts will execute in their browsers, potentially leading to theft of sensitive information, session hijacking, or other malicious actions.

Because the vulnerability is a Stored Cross-Site Scripting issue, the malicious code persists on the site and affects all users who access the compromised content.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart