The Post Snippets – Custom WordPress Code Snippets Customizer plugin for WordPress is vulnerable to Stored Cross-Site
Source GCVE Database
Not known to be exploited · CVSS 6.4 Medium.
Data as of 28 Oct 2026, 10:14 UTC
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 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| saadiqbalPost Snippets – Custom WordPress Code Snippets Customizer | Affected
| Fixed in– |
AI-suggested
Since the vulnerability requires snippet shortcodes to be enabled, disabling snippet shortcodes can mitigate the risk. Users should monitor the vendor's advisory for patch releases and apply updates once available. Until then, restrict contributor-level access and consider disabling or limiting shortcode usage.
Description
The Post Snippets WordPress plugin up to version 4.2.4 is vulnerable to stored cross-site scripting (XSS) via shortcode attributes. Authenticated users with contributor-level access or higher can inject malicious scripts that execute when other users view the affected pages. The vulnerability arises from insufficient input sanitization and output escaping, allowing entity-encoded payloads to bypass WordPress's standard sanitization and be executed at render time by the plugin's shortcode filter. This requires snippet shortcodes to be enabled.
References
- nvd.nist.gov/vuln/detail/CVE-2026-77871 (opens in a new tab)
- plugins.trac.wordpress.org/browser/post-snippets/tags/4.2.3/src/PostSnippets/Shortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/post-snippets/tags/4.2.3/src/PostSnippets/Shortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/post-snippets/tags/4.2.3/src/PostSnippets/Shortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/post-snippets/tags/4.2.3/src/PostSnippets/Shortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/post-snippets/tags/4.2.4/src/PostSnippets/Shortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/post-snippets/tags/4.2.4/src/PostSnippets/Shortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/post-snippets/tags/4.2.4/src/PostSnippets/Shortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/post-snippets/tags/4.2.4/src/PostSnippets/Shortcode.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3759640/post-snippets/trunk/src/PostSnippets/Shortcode.php (opens in a new tab)
- wordfence.com/threat-intel/vulnerabilities/id/a46c37f4-245d-423f-bdad-296fdf377ecc?source=cve (opens in a new tab)