CVE-2026-3554: Sherk Custom Post Type Displays (WordPress plugin) · Cross-site Scripting
Affects Sherk Custom Post Type Displays (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| sherkspearSherk Custom Post Type Displays | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, administrators should consider restricting Contributor-level access or higher to trusted users only and avoid using the vulnerable shortcode with untrusted input. Monitoring for plugin updates from the vendor is recommended to apply any forthcoming official fixes.
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/d227d4e4-2899-434c-8b93-8d93a89b1b1b?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/sherk-custom-post-type-displays/trunk/includes/SherkCPTDisplaysShortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/sherk-custom-post-type-displays/tags/1.2.1/includes/SherkCPTDisplaysShortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/sherk-custom-post-type-displays/trunk/includes/SherkCPTDisplaysShortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/sherk-custom-post-type-displays/tags/1.2.1/includes/SherkCPTDisplaysShortcode.php (opens in a new tab)