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

CVE-2026-3004

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable 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 Snow Monkey Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘data-slick' attribute in all versions up to, and including, 24.1.11 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.

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 Snow Monkey Blocks WordPress plugin fails to properly sanitize and escape the 'data-slick' attribute, allowing authenticated users with Contributor-level permissions or higher to inject malicious JavaScript code that persists on affected pages and executes when visitors access those pages.

MitigationUpdate the Snow Monkey Blocks plugin to version 24.1.12 or later, which includes proper input sanitization and output escaping for the data-slick attribute to prevent XSS injection.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Snow Monkey Blocks plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Snow Monkey Blocks' in the list. Alternatively, check the /wp-content/plugins/snow-monkey-blocks/ directory existence.
    Affected if Plugin is installed and active
  2. Determine installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the Snow Monkey Blocks plugin to view its version number. Or read the main plugin PHP file header for the Version field.
    Affected if Version is lower than 24.1.12
  3. Identify pages using the data-slick attribute
    Search the WordPress database or page content for occurrences of 'data-slick' in postmeta table or in page/post content. Alternatively, inspect page source of published content blocks that use slider/carousel components.
    Affected if Pages or posts contain the data-slick attribute in their rendered output
  4. Check for unexpected script injections in page content
    Review page/post content in the WordPress editor for any injected <script> tags or javascript: URLs within data-slick attribute values, or inspect the HTML source of affected pages for suspicious script references.
    Affected if Malicious JavaScript code is present in data-slick attribute values

User is affected if Snow Monkey Blocks plugin version is below 24.1.12 AND the data-slick feature is being used on any published pages, potentially containing injected malicious scripts.

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

Update the Snow Monkey Blocks plugin to version 24.1.12 or later, which includes proper input sanitization and output escaping for the data-slick attribute to prevent XSS injection.

Recommended fix Moderate confidence

Update Snow Monkey Blocks to version 24.1.12 or later

  1. 1. Log in to the WordPress admin dashboard with Administrator access
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Snow Monkey Blocks plugin in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 24.1.12 or later
  6. 6. Test affected functionality to ensure the update did not break existing features
  7. 7. Clear any caching mechanisms if the site uses caching plugins

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3004 — 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-3004 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