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

CVE-2026-3011

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-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

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 Recipe Card Blocks Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the recipe block's 'summary' and 'notes' attributes in all versions up to, and including, 3.4.13. This is due to the 'WPZOOM_Helpers::deserialize_block_attributes' method converting unicode-encoded sequences back into HTML characters after sanitization has already been applied. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that execute whenever a user accesses the published post or the print view of an injected recipe.

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 Recipe Card Blocks Lite WordPress plugin has a stored XSS vulnerability in the recipe block's 'summary' and 'notes' fields. The `WPZOOM_Helpers::deserialize_block_attributes` method converts unicode-encoded sequences back into HTML characters after sanitization has already been applied, effectively bypassing the sanitization. Authenticated attackers with Author-level access or higher can inject malicious JavaScript that executes when users view the published recipe or its print view.

MitigationUpdate to version 3.4.14 or later when available; audit existing recipes for malicious content; apply output encoding at render time as defense-in-depth.

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. Check installed plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > Recipe Card Blocks Lite. The version number is displayed below the plugin name.
    Affected if The installed version is 3.4.13 or lower.
  2. Verify plugin is active
    In the Plugins list, confirm Recipe Card Blocks Lite shows as 'Active' under the status column.
    Affected if The plugin is active and vulnerable version is installed.
  3. Inspect posts for recipe blocks
    Query the WordPress database: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%<!-- wp:wpzoom-recipe-card%' AND post_status='publish'; Or use WP-CLI: wp post list --post_type=any --field=ID | xargs -I{} wp post get {} --format=json | jq -r 'select(.content.rendered | contains("wpzoom-recipe-card")) .ID'
    Affected if Published posts contain recipe blocks with the vulnerable block structure.
  4. Examine summary and notes fields
    Search post content for the 'summary' and 'notes' attributes within recipe blocks. These are stored in post meta or block attributes. Check for presence of unicode escape sequences (\u) or encoded content that may represent bypassed sanitization.
    Affected if Recipe blocks contain non-empty 'summary' or 'notes' attributes.
  5. Audit Author-level and higher users
    Navigate to Users > All Users in WordPress admin. Review the list for accounts with Author, Editor, or Administrator roles.
    Affected if There are user accounts with Author-level or higher access who could have injected malicious content.

A user is affected if Recipe Card Blocks Lite version 3.4.13 or lower is active and published posts contain recipe blocks with populated summary or notes fields that may contain sanitization-bypassing unicode sequences.

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 to version 3.4.14 or later when available; audit existing recipes for malicious content; apply output encoding at render time as defense-in-depth.

Recommended fix High confidence

Recipe Card Blocks Lite version 3.4.14 or later

  1. 1. Log in to WordPress admin dashboard with Author-level or higher privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Recipe Card Blocks by WPZOOM' in the plugin list
  4. 4. Check if an update is available for the plugin
  5. 5. If update available, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the latest version from wordpress.org/plugins/recipe-card-blocks/ and upload via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the version number is 3.4.14 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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