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

CVE-2026-57764

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
Contributor Cross Site Scripting (XSS) in Surbma | Yoast SEO Breadcrumb Shortcode <= 1.2 versions.

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

A stored Cross Site Scripting (XSS) vulnerability exists in the Surbma | Yoast SEO Breadcrumb Shortcode WordPress plugin affecting versions 1.2 and below. Authenticated users with Contributor-level permissions can inject malicious scripts through the plugin's shortcode functionality, which are then executed when other users view the affected content.

MitigationUpdate the plugin to the latest version beyond 1.2 which should contain proper input sanitization and output encoding for the shortcode parameters. If no patched version is available, disable the plugin until a fix is released.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

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 the plugin is installed
    Check the WordPress plugins directory or wp-admin/plugins.php for 'Surbma | Yoast SEO Breadcrumb Shortcode' plugin presence
    Affected if plugin is installed and active
  2. Determine installed plugin version
    Access the plugin file header via wp-admin/plugins.php or inspect the main plugin file (usually in wp-content/plugins/surbma-yoast-seo-breadcrumb-shortcode/) for the Version comment
    Affected if version is 1.2 or below
  3. Confirm shortcode is in use
    Search WordPress database posts table for '[surbma_yoast_breadcrumb]' or similar shortcode usage, or check page content for rendered breadcrumb output
    Affected if shortcode is present in any published content
  4. Assess user permission exposure
    Review WordPress user roles to identify accounts with Contributor-level or higher access via wp-admin/users.php
    Affected if any accounts with Contributor, Author, Editor, or Administrator roles exist (these roles can exploit the vulnerability)
  5. Inspect content for suspicious script injection
    Examine post content containing the shortcode for unusual script tags, event handlers (onload, onerror, onclick), or javascript: URIs in shortcode parameters
    Affected if any such patterns are found in content using the plugin shortcode

User is affected if the plugin is installed with version 1.2 or below and any shortcode usage exists with untrusted contributor-level authors.

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 the plugin to the latest version beyond 1.2 which should contain proper input sanitization and output encoding for the shortcode parameters. If no patched version is available, disable the plugin until a fix is released.

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