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

CVE-2026-6740

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-08
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 6 weeks old

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 Nexter Blocks – Gutenberg Blocks, Page Builder & AI Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'commentIcon' parameter in all versions up to, and including, 4.7.4 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 Nexter Blocks WordPress plugin versions up to 4.7.4 have a stored XSS vulnerability in the 'commentIcon' parameter. Authenticated users with contributor-level access can inject arbitrary JavaScript through insufficient input sanitization, which executes when other users access affected pages.

MitigationUpdate the plugin to version 4.7.5 or later, which includes proper input sanitization and output escaping for the commentIcon parameter.

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 Nexter Blocks plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Nexter Blocks' in the list. Note the installed version number displayed below the plugin name.
    Affected if Plugin is installed and version is 4.7.4 or lower
  2. Compare installed version to affected range
    Check the version number from step 1 against the affected range. The vulnerability exists in versions up to and including 4.7.4.
    Affected if Installed version is 4.7.4 or lower (any version below 4.7.5)
  3. Identify users with contributor-level access
    In WordPress admin, go to Users > All Users and review the Role column. Look for any users assigned the 'Contributor' role.
    Affected if Any user with Contributor role exists on the site
  4. Inspect commentIcon parameter usage
    Query the WordPress database for posts/pages containing the commentIcon metadata. Run: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%commentIcon%' (adjust prefix if different).
    Affected if Records exist in postmeta table with commentIcon metadata containing unsanitized values

The environment is affected if the Nexter Blocks plugin version is 4.7.4 or lower AND any user with Contributor role exists AND the commentIcon feature has been used in any content.

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 plugin to version 4.7.5 or later, which includes proper input sanitization and output escaping for the commentIcon parameter.

Recommended fix Moderate confidence

Version 4.7.5 or later

  1. 1. Log in to the WordPress admin dashboard with contributor-level or higher privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Nexter Blocks – Gutenberg Blocks, Page Builder & AI Website Builder' 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 4.7.5 or higher under Plugins > Installed 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
  • 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-6740 — 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-6740 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