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

CVE-2026-9756

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-03
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 7 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 GenerateBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Headline Block 'linkMetaFieldType' Dynamic Link Attribute in all versions up to, and including, 2.2.1 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. A contributor-level attacker can store a JavaScript payload in their own profile description (allowlisted by get_safe_user_meta_keys()) and prepend 'javascript:' via the linkMetaFieldType attribute, creating a fully attacker-controlled href that executes when any user, including an administrator, clicks the rendered headline link.

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 · moderate confidence

The GenerateBlocks WordPress plugin up to version 2.2.1 has a stored XSS vulnerability in the Headline Block's linkMetaFieldType dynamic link attribute. Authenticated contributors can inject JavaScript payloads by storing them in their user profile description (via get_safe_user_meta_keys()) and prepending 'javascript:' to the link attribute, causing arbitrary script execution when administrators click the rendered link.

MitigationUpdate GenerateBlocks to the latest version once available, or temporarily restrict contributor-level user creation and audit existing contributor accounts.

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 GenerateBlocks plugin installation
    Check the WordPress plugins list or inspect the GenerateBlocks plugin header for the installed version number
    Affected if GenerateBlocks plugin is installed and the version is 2.2.1 or lower
  2. Identify active Headline Blocks with dynamic links
    Search post content for Headline blocks that contain link attributes, particularly those using dynamic data sources like user meta
    Affected if Headline Blocks are present with dynamic link attributes pointing to user profile fields
  3. Enumerate contributor-level user accounts
    In WordPress admin, go to Users > All Users and filter by Contributor role, or query the wp_users and wp_usermeta tables for users with contributor capabilities
    Affected if Any contributor-level user accounts exist in the WordPress installation
  4. Inspect user meta for suspicious values
    Query the wp_usermeta table for meta_keys containing user-provided fields (such as description or bio), looking for values prefixed with 'javascript:' or containing script tags
    Affected if Any user meta fields contain 'javascript:' protocols or HTML/script content that could be injected into links
  5. Review rendered Headline Block output
    View pages containing Headline Blocks as an administrator and inspect the HTML source for dynamically generated links
    Affected if Rendered links contain 'javascript:' protocols or unescaped user-provided content in href attributes

A user is affected if GenerateBlocks version 2.2.1 or lower is installed, the Headline Block is used with dynamic link attributes sourcing from user profile fields, and at least one contributor account exists with injectable meta 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.

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

Update GenerateBlocks to the latest version once available, or temporarily restrict contributor-level user creation and audit existing contributor accounts.

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-9756 — 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-9756 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