Plugins · post-snippets · data as of 2026-11-04
Is Post Snippets safe? Known vulnerabilities and latest version
- Status
- Closed 2026-09-30
- Known issues on record
- 8
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate post-snippets && wp plugin delete post-snippets
Check your version
Known vulnerabilities
8 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 8 record(s) do not state which versions are affected.
medium 6.4 CVE-2026-77871 · published 2026-10-28
Stored cross-site scripting (XSS) in Post Snippets (4.2.4 and older)
- Affected
- 4.2.4 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-77871Wordfence advisoryCode change (fix)Plugin source
medium 6.8 CVE-2026-12980 · published 2026-10-11
Cross-site scripting (XSS) in Post Snippets (4.2.4 and older)
- Affected
- 4.2.4 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
The Post Snippets WordPress plugin through 4.2.4 does not properly escape variable values substituted into snippets before outputting them, allowing users with the Contributor role and above to inject arbitrary web scripts that execute when the content is viewed.
high 8.5 CVE-2026-56049 · published 2026-06-25
Remote code execution in Post Snippets (4.0.19 and older)
- Affected
- 4.0.19 and older
- Fixed in
- 4.1.0
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Contributor Remote Code Execution (RCE) in Post Snippets <= 4.0.19 versions.
medium 4.4 CVE-2026-7430 · published 2026-05-29
Stored cross-site scripting (XSS) in Post Snippets (4.0.19 and older)
- Affected
- 4.0.19 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Post Snippets plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 4.0.19. This is due to insufficient output escaping of imported snippet content when rendering JavaScript variables in the post editor. Specifically, the `jqueryUiDialog()` method in `WPEditor.php` embeds snippet content directly into JavaScript string literals without escaping double quotes (the quote-escaping code on line 214 is commented out). When snippets are imported via the Import/Export feature, the content bypasses WordPress's `wp_magic_quotes()` (which would otherwise add protective backslashes), allowing double quotes in snippet content to break out of the JavaScript string context. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts via a malicious import file that execute whenever any administrator accesses a post editor page. Please note that this does not affect single-site installations as administrators already have the `unfiltered_html` capability.
high 8.5 CVE-2026-25001 · published 2026-03-25
Remote code execution in Post Snippets (4.0.12 and older)
- Affected
- 4.0.12 and older
- Fixed in
- 4.0.13
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Control of Generation of Code ('Code Injection') vulnerability in Saad Iqbal Post Snippets post-snippets allows Remote Code Inclusion.This issue affects Post Snippets: from n/a through <= 4.0.12.
medium 4.3 CVE-2025-63040 · published 2025-12-31
Cross-site request forgery (CSRF) in Post Snippets (4.0.11 and older)
- Affected
- 4.0.11 and older
- Fixed in
- 4.0.12
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Saad Iqbal Post Snippets post-snippets allows Cross Site Request Forgery.This issue affects Post Snippets: from n/a through <= 4.0.11.
medium 4.8 CVE-2023-25459 · published 2023-08-08
Stored cross-site scripting (XSS) in Post Snippets (4.0.2 and older)
- Affected
- 4.0.2 and older
- Fixed in
- 4.0.3
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Postsnippets Post Snippets plugin <= 4.0.2 versions.
critical 9.6 CVE-2021-25010 · published 2022-02-28
Cross-site request forgery (CSRF) in Post Snippets (older than 3.1.4)
- Affected
- older than 3.1.4
- Fixed in
- 3.1.4
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The Post Snippets WordPress plugin before 3.1.4 does not have CSRF check when importing files, allowing attacker to make a logged In admin import arbitrary snippets. Furthermore, imported snippers are not sanitised and escaped, which could lead to Stored Cross-Site Scripting issues
Recent activity
- 2026-09-30 — closed on wordpress.org.
- 2026-10-28 — Stored cross-site scripting (XSS) disclosed (CVE-2026-77871), fix version not stated.
- 2026-10-11 — Cross-site scripting (XSS) disclosed (CVE-2026-12980), fix version not stated.
- 2026-06-25 — Remote code execution disclosed (CVE-2026-56049), fixed in 4.1.0.
Get an email when Post Snippets has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Post Snippets (post-snippets) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (4) · Remote code execution (2) · Cross-site request forgery (CSRF) (2)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/post-snippets (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/post-snippets"><img src="https://laskyr.com/plugins/post-snippets/badge.svg" alt="Post Snippets vulnerability status"></a>