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

CVE-2026-6247

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-12
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 scratchblocks for WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'element' attribute of the 'scratchblocks' shortcode in all versions up to, and including, 1.0.1 due to insufficient input sanitization and output escaping on user supplied attributes. 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 scratchblocks WordPress plugin fails to sanitize and escape user-supplied attributes in the 'scratchblocks' shortcode, specifically the 'element' attribute. Authenticated attackers with contributor-level access can inject malicious JavaScript that persists on affected pages and executes whenever users access those pages.

MitigationImplement proper input sanitization and output escaping for shortcode attributes using WordPress functions like esc_attr() and sanitize_text_field(); update to patched version once available.

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 scratchblocks plugin installation and version
    Navigate to WordPress admin > Plugins and locate scratchblocks. Note the installed version number, then compare it against any known affected version ranges.
    Affected if The plugin is installed and running a version that falls within the affected range.
  2. Identify all posts and pages using the scratchblocks shortcode
    Search the WordPress database (wp_posts table) or use a plugin to find all content containing the shortcode [scratchblocks]. Look for variations like [scratchblocks element="..."] or [scratchblocks element='...'].
    Affected if Any post or page contains the scratchblocks shortcode.
  3. Inspect the element attribute values in shortcode usage
    Examine each found shortcode for the 'element' attribute. Manually review the attribute value for any unescaped characters such as <, >, ", ', or JavaScript event handlers (onclick, onerror, etc.).
    Affected if The 'element' attribute contains unescaped HTML, JavaScript code, or event handler syntax.
  4. Check for stored malicious scripts in affected content
    View the source of pages containing the scratchblocks shortcode. Look for any script tags or event handlers that appear within the element attribute context.
    Affected if Malicious JavaScript code is present in the rendered HTML and executes in user browsers.
  5. Review user roles with contributor access
    Go to WordPress admin > Users and identify accounts with Contributor role or higher. These users can edit posts and potentially exploit the vulnerability.
    Affected if Any authenticated user with Contributor-level access exists in the system.

You are affected if the scratchblocks plugin is installed and any page or post contains the scratchblocks shortcode with a crafted 'element' attribute containing unescaped JavaScript or HTML.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input sanitization and output escaping for shortcode attributes using WordPress functions like esc_attr() and sanitize_text_field(); update to patched version once available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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