CVE-2026-12980: Post Snippets cross-site scripting (XSS) vulnerability
medium 6.8 plugin closed published 2026-10-11 · updated 2026-10-13
- Affected versions
- 4.2.4 and older
- Fixed in
- unknown
- Severity
- Medium · CVSS 6.8
- Active installs
- closed
- Type
- Cross-site scripting (XSS)
What an attacker needs
- Access: An admin-level account (per the CVSS score).
- Interaction: It also needs someone on the site (often an admin) to click a link, open a page or submit a form the attacker prepared.
CVSS vector (score by CISA ADP): CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
What to do now
- Replace Post Snippets. A closed plugin gets no updates through WordPress, so this hole stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deactivating alone leaves its files on the server.
- Not sure which version you run? Check your version against every known Post Snippets issue.
- If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.
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.
References
- NVD CVE-2026-12980 nvd.nist.gov
- WPScan advisory wpscan.com
Related
Ran an affected version? Check your site for signs of a hack
The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.
Already hacked? Flat $499 cleanup with a 30-day reinfection guarantee.
Where this data comes from
- CVE record, score and references: 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.
- Versions and install counts: wordpress.org/plugins/post-snippets (Plugins API), fetched 2026-11-04.
- The summary, “what an attacker needs” and “what to do” sections are our plain-English reading of the record and the plugin's release history; the quoted description is the record's own text. Spot an error? Email Daniel.