CVE-2026-3554
Received Received - Intake
Stored XSS in Sherk Custom Post Type Displays WordPress Plugin

Publication date: 2026-03-21

Last updated on: 2026-03-21

Assigner: Wordfence

Description
The Sherk Custom Post Type Displays plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title' shortcode attribute in all versions up to, and including, 1.2.1. This is due to insufficient input sanitization and output escaping on the 'title' attribute of the 'sherkcptdisplays' shortcode. Specifically, in the sherkcptdisplays_func() function in includes/SherkCPTDisplaysShortcode.php, the 'title' attribute value is extracted from shortcode_atts() on line 19 and directly concatenated into an HTML <h2> tag on line 31 without any escaping. 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-27
AI Q&A
2026-03-21
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
sherk_custom_post_type_displays sherk_custom_post_type_displays to 1.2.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 Sherk Custom Post Type Displays plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in its 'title' shortcode attribute in all versions up to and including 1.2.1.

This vulnerability occurs because the plugin does not properly sanitize or escape the input provided in the 'title' attribute of the 'sherkcptdisplays' shortcode.

Specifically, the 'title' attribute value is taken directly from user input and inserted into an HTML <h2> tag without escaping, allowing an attacker with Contributor-level access or higher to inject malicious scripts.

These scripts then execute whenever any user views the affected page, potentially compromising user data or site integrity.


How can this vulnerability impact me? :

This vulnerability allows authenticated attackers with Contributor-level access or higher to inject arbitrary malicious scripts into pages.

When other users visit these pages, the injected scripts execute in their browsers, which can lead to theft of sensitive information, session hijacking, or unauthorized actions performed on behalf of the user.

Because the attack is stored, the malicious code persists on the site and affects all visitors to the compromised pages.


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