dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-3876

HIGH · 7.2 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Prismatic WordPress plugin fails to properly sanitize and escape user input in the prismatic_decode function, allowing unauthenticated attackers to inject malicious JavaScript via crafted prismatic_encoded pseudo-shortcodes embedded in comments. This stored XSS executes whenever users access pages containing the injected shortcode.

MitigationUpgrade Prismatic plugin to version 3.7.4 or later. The fix requires adding proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_html, esc_attr) to all user-supplied attributes processed by prismatic_decode.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Prismatic plugin is installed and active
    In WordPress admin, go to Plugins > Installed Plugins and verify Prismatic appears in the active plugins list, or query the wp_options table: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins'
    Affected if Prismatic plugin is not installed or is not active - no risk from this CVE
  2. Identify installed Prismatic version
    Check the plugin header in wp-content/plugins/prismatic/prismatic.php for 'Version:' value, or query the wp_options table: SELECT option_value FROM wp_options WHERE option_name = 'prismatic_version'
    Affected if Version is present and less than 3.7.4 - vulnerable to this CVE
  3. Verify WordPress comments are enabled
    Go to Settings > Discussion in WordPress admin, or query: SELECT option_value FROM wp_options WHERE option_name = 'default_comment_status'
    Affected if Comments are open and the plugin version is below 3.7.4 - attack surface is active
  4. Inspect recent comments for malicious prismatic_encoded shortcodes
    Query the wp_comments table for patterns containing 'prismatic_encoded': SELECT comment_ID, comment_author, SUBSTRING(comment_content, 1, 200) FROM wp_comments WHERE comment_content LIKE '%prismatic_encoded%'
    Affected if Any comments contain prismatic_encoded pseudo-shortcode patterns - indicates potential exploitation

User is affected if Prismatic plugin is installed with version less than 3.7.4 AND comments are enabled on the site, allowing the stored XSS to be injected and executed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Prismatic plugin to version 3.7.4 or later. The fix requires adding proper input sanitization (e.g., sanitize_text_field) and output escaping (e.g., esc_html, esc_attr) to all user-supplied attributes processed by prismatic_decode.

Recommended fix High confidence

Plugin version 3.7.4 or later

  1. Upgrade the Prismatic WordPress plugin to version 3.7.4 or later
  2. Verify the upgrade was successful by checking the plugin version in WordPress admin under Plugins > Installed Plugins
  3. Test that the plugin functionality still works as expected after the upgrade
  4. Review comments and content on the site to ensure no malicious 'prismatic_encoded' shortcodes were injected prior to the upgrade and remove any found

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3876 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3876 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data