Live › vulnerability › CVE-2026-77871
Go to dashboardThe Post Snippets WordPress plugin up to and including 4.2.4 fails to sanitize shortcode attributes, so entity-encoded script tags survive save and are decoded into live HTML at render time. An authenticated contributor can plant JavaScript that runs in the browser of anyone who views the affected page, including administrators.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 07:31 UTC. All times on this page are UTC.
Sites running the Post Snippets plugin at version 4.2.4 or earlier with snippet shortcodes enabled. Exposure requires an account with contributor-level access or higher, so sites with no untrusted contributors carry lower risk. Sites without the plugin, or with shortcodes disabled, can skip it.
No product ranges from the sources yet.
4.2.4 and below are affected.4.2.4, as the sources do not name a fixed version.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Post Snippets – Custom WordPress Code Snippets Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Shortcode Attributes in all versions up to, and including, 4.2.4 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. Entity-encoded payloads such as <script>...</script> survive WordPress's wp_kses_post on-save sanitization because kses does not decode HTML entities, and are only converted back into executable HTML tags at render time by the plugin's own shortcode filter. This requires snippet shortcodes to be enabled.
This page as .md · .json · in your agent: get_signal("CVE-2026-77871")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.