Shortcodify contributors can store script through the section shortcode
Shortcodify through 1.4.3 allows a Contributor or higher to place attacker-controlled markup in the name attribute of the [section] shortcode. createAccordionSection() concatenates that value directly into an h3 element without sanitization or output escaping, so the payload executes in the site origin when the affected content is rendered. The official WordPress.org tags and trunk currently stop at 1.4.3 and retain the vulnerable code; no fixed release or patched function is disclosed.
- Component
- Shortcodify
- Plugin slug
shortcodify- Affected
- <= 1.4.3
- Safe version
- See mitigation notes
- Published
- Jul 28, 2026
This CVE was published Jul 28, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
No patched release is currently available. Deactivate Shortcodify if it is not essential, or apply an upstream fix once released; meanwhile review Contributor-authored [section] shortcodes and avoid rendering untrusted drafts to privileged users.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Shortcodify plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'name' Shortcode Attribute in all versions up to, and including, 1.4.3 due to insufficient input sanitization and output 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N