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

CVE-2026-3498

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-11
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 BlockArt Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'clientId' block attribute in all versions up to, and including, 2.2.15. This is due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Author-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 BlockArt Blocks WordPress plugin (versions up to 2.2.15) has a stored XSS vulnerability in the 'clientId' block attribute. Insufficient input sanitization on user-supplied clientId values combined with inadequate output escaping allows authenticated attackers with Author-level permissions or higher to inject arbitrary JavaScript that executes when other users view infected pages.

MitigationUpdate BlockArt Blocks to the latest version after confirming a patch exists, or implement proper sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) on all clientId attribute handling in the plugin code.

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. Confirm BlockArt Blocks plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'BlockArt Blocks' to verify the plugin is active on the site
    Affected if BlockArt Blocks plugin is found and active
  2. Check installed BlockArt Blocks version
    On the Plugins page, find BlockArt Blocks and note the version number displayed in the plugin meta. Compare this version to the affected range (versions up to 2.2.15)
    Affected if Installed version is 2.2.15 or lower, indicating the unpatched version
  3. Identify if clientId block attribute is in use
    Search the WordPress database (wp_posts table) or export content for occurrences of the clientId attribute within block markup. This can be done via WP-CLI: wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%clientId%'" or by examining page/post content where BlockArt blocks were used
    Affected if Content contains blocks with clientId attributes, meaning the vulnerable attribute is present and could harbor malicious scripts
  4. Assess user permission exposure
    Review user roles on the site via Users > All Users in the admin panel. Determine if any accounts with Author-level or higher permissions exist who may have injected malicious clientId values
    Affected if Users with Author, Editor, or Administrator roles exist, as these roles could have exploited the vulnerability to inject stored XSS

You are affected if BlockArt Blocks plugin is installed with version 2.2.15 or lower AND your site content contains BlockArt blocks utilizing the clientId attribute, particularly if you have users with Author-level or higher permissions.

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 BlockArt Blocks to the latest version after confirming a patch exists, or implement proper sanitization (sanitize_text_field) and output escaping (esc_attr/esc_html) on all clientId attribute handling in the plugin code.

Recommended fix Moderate confidence

BlockArt Blocks version 2.2.16 or later

  1. Check the current version of the BlockArt Blocks plugin in WordPress admin under Plugins > Installed Plugins
  2. Navigate to Plugins > Add New > Upload Plugin or update directly from the Plugins page if an update is available
  3. Verify the installed version is higher than 2.2.15 after updating
  4. Clear any caching mechanisms if the site uses caching
  5. Test that the BlockArt Blocks editor functionality works correctly after the update
  6. Review pages using BlockArt Blocks to ensure no malicious scripts were injected prior to the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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