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

CVE-2026-6252

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-14
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 Meta Field Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'tagName' block attribute in all versions up to, and including, 1.5.2 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 Meta Field Block plugin for WordPress has a stored XSS vulnerability in the 'tagName' block attribute. Due to insufficient input sanitization and output escaping, authenticated users with contributor-level access or higher can inject arbitrary JavaScript that persists on pages and executes whenever users access those pages.

MitigationUpdate to the latest version of the Meta Field Block plugin when available. Review and remediate existing content for injected scripts, and limit user permissions pending the patch.

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 Meta Field Block plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Meta Field Block' in the list. Note the version number displayed.
    Affected if The plugin is installed and active
  2. Check installed version against affected range
    Compare your installed version number to the affected versions. Since no specific version range is provided in the CVE, assume versions prior to the patch may be vulnerable.
    Affected if Your version is older than the patched version (when known)
  3. Identify contributor-level or higher users
    Go to Users > All Users in WordPress admin. Review the Role column for any users with Contributor, Author, Editor, or Administrator roles.
    Affected if Any user account with contributor-level or higher access exists on the site
  4. Inspect pages for Meta Field Block usage
    Edit a page or post. Look for the Meta Field Block in the block editor. Select the block and inspect its attributes panel for the 'tagName' field.
    Affected if The Meta Field Block with a tagName attribute is present in published content
  5. Examine block content for injected scripts
    Switch to Code Editor view (three-dot menu > Code Editor) or view page source. Search for script tags, javascript: URIs, or event handlers (onclick, onerror, onload) within block attributes or content.
    Affected if Unexpected script tags or event handlers are found in Meta Field Block data

A user is affected if the Meta Field Block plugin is installed, the installed version is unpatched, and pages contain the vulnerable block with injected malicious code.

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 the latest version of the Meta Field Block plugin when available. Review and remediate existing content for injected scripts, and limit user permissions pending the patch.

Recommended fix High confidence

Latest version greater than 1.5.2 (check WordPress plugin repository for current stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Meta Field Block' plugin
  4. Click 'Update Now' if an update is available, or manually download the latest version from plugins.trac.wordpress.org and upload it
  5. After updating, verify the plugin version is greater than 1.5.2

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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