Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level account
-
DeliveryInject unescaped script into snippet variable
-
ExploitAdmin views rendered snippet content
-
ExecutionScript executes in admin browser session
-
ImpactHijack session or create rogue admin
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with the Contributor role or higher on a site running Post Snippets ≤4.2.4, plus a victim (typically a higher-privileged user such as an editor/administrator) who subsequently views the content where the snippet's unescaped variable values are rendered (UI:R). Exploitation is therefore limited to deployments that grant snippet-authoring/contributor access to untrusted or lower-trust users; sites restricting content authoring to trusted administrators are not realistically exposed. No non-default plugin setting is required beyond having the plugin active and snippets in use. |
| Impact | This is a stored/injected XSS (CWE-79) in the Post Snippets WordPress plugin through 4.2.4, requiring an authenticated user with Contributor role or above. The input CVSS vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H, 6.8) is internally inconsistent with the description: it marks PR:H (high privilege) yet the description states Contributor-level access suffices, which is a LOW-privilege authenticated role - PR:L is more defensible. It also assigns C:H/I:H/A:H and S:U, which overstates impact for a typical reflected/stored script-injection flaw where real impact is usually limited (C:L/I:L) and scope typically changes (S:C) because the script executes in a victim's browser context. A public exploit exists (publicly available exploit code exists, reported by WPScan), but there is no CISA KEV listing and no EPSS score was provided, so there is no evidence of active or widespread exploitation - treat POC availability and active exploitation as distinct signals. Net real-world risk is moderate-but-conditional: exploitation needs an authenticated contributor account AND a victim (typically an admin/editor) to view the malicious snippet output. For sites that allow untrusted contributors this is a meaningful privilege-escalation-to-admin vector; for single-author or tightly-controlled sites the practical risk is low. |
| Exploit ScenarioDerived | A site permits untrusted users to register at Contributor level. An attacker with such an account crafts a snippet whose variable values contain unescaped JavaScript; when an administrator or editor previews or publishes content that renders the snippet, the script executes in their authenticated session. A public exploit/PoC is available via WPScan, lowering the effort to reproduce the attack. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Stored cross-site scripting in the Post Snippets WordPress plugin through 4.2.4 lets an authenticated user with Contributor-level access or above inject arbitrary JavaScript through snippet variable values, which then executes in the browser of any higher-privileged user (such as an editor or administrator) who views the rendered content. The plugin substitutes variable values into snippet output without escaping them, so injected script runs in the context of the viewing user's session and can be leveraged for session or credential theft and privileged actions performed on the victim's behalf. Publicly available exploit code exists and WPScan published the vulnerability, but there is no evidence of confirmed active exploitation (the issue is not in CISA KEV); real-world exposure is limited to sites that grant Contributor or snippet-authoring access to untrusted or lower-trust users.
RemediationAI
No vendor-released patch was identified at time of analysis for CVE-2026-12980; Post Snippets through 4.2.4 remains the affected range, so check the plugin's update channel and install any release newer than 4.2.4 if and when it appears, and consult the WPScan advisory at https://wpscan.com/vulnerability/288d419a-9e27-45ae-bde1-1aef52532354/ for updated fix information. Until a fixed version is confirmed, the most effective control is to remove the attack precondition: revoke Contributor or any snippet-authoring capability from untrusted users (using a role-management plugin to deny snippet access to Contributor and below), which neutralizes the issue but changes editorial workflows for those accounts. As compensating measures, audit existing snippets and user accounts with Contributor-and-above access for injected markup and remove anything suspicious, restrict who can create or edit snippets to administrators only, consider a Content Security Policy that blocks inline and third-party script execution (with the trade-off that it can break legitimate theme/plugin JavaScript), and deploy WAF rules that inspect snippet rendering output for script tags or event handlers (subject to false positives on legitimate markup). Where snippet authoring cannot be locked down, temporarily disabling the Post Snippets plugin eliminates the exposure at the cost of losing all snippet functionality on the site.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Post Snippets is a WordPress plugin that allows site owners to define reusable snippets (shortcodes and PHP-like variables) that are expanded and rendered inside posts, pages, and widgets. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), and specifically a context problem: the plugin sanitizes or stores variable values but does not apply output escaping at the point where those values are substituted into the snippet markup before it is echoed to the page, so any markup present in the value is emitted as live HTML/JavaScript. Correct handling requires contextual output escaping applied after substitution (for example esc_html(), esc_attr(), or wp_kses_post() depending on the sink) rather than relying on input filtering alone. The CPE record cpe:2.3:a:unknown:post_snippets:*:*:*:*:*:*:*:* identifies the plugin with a wildcard version and an unresolved vendor namespace, and EUVD records affected versions as 'Post Snippets 0 through 4.2.4'. Note the scoring divergence: the vendor/NVD-style vector CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H (6.8) assumes high privileges and unchanged scope, while the independent assessment uses CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, reflecting Contributor-level (low) privileges and scope change because the script executes in the victim's browser context; both agree on network vector, low attack complexity, and required user interaction.
Know when Post Snippets gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Contributor is a low-privileged authenticated role so PR:L (not PR:H); victim must view content (UI:R); script runs in another user's context so S:C with limited C:L/I:L and no availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Post Snippets
View allThe Post Snippets WordPress plugin versions up to and including 4.0.12 contain an improper code generation vulnerability
Remote code execution in the Post Snippets WordPress plugin (versions 4.0.19 and earlier) lets an authenticated user wit
Auth. Rated medium severity (CVSS 4.8), this vulnerability is remotely exploitable, low attack complexity. No vendor pat
EUVD-2026-96733
GHSA-qq38-mwrv-h27q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB