Description
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.
Published: 2026-05-14
Score: 6.4 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

This vulnerability arises from a lack of input sanitization and output escaping for the 'tagName' attribute of blocks in the Meta Field Block plugin. Attackers who possess contributor or higher privileges can store arbitrary JavaScript in this attribute. When a page containing the malicious block is viewed, the injected script executes in the context of any user who visits the page, potentially enabling cookie theft, session hijacking, defacement, or other malicious actions. The weakness is a classic reflected or stored cross‑site scripting flaw (CWE‑79).

Affected Systems

The Meta Field Block WordPress plugin, versions up to and including 1.5.2. Affected installations run WordPress and have this plugin configured; users with contributor-level access or higher can inject the payload via the block editor.

Risk and Exploitability

The CVSS score of 6.4 indicates moderate severity. No EPSS score is available, and the vulnerability is not listed in CISA’s KEV catalog, suggesting no widespread, actively exploited instances reported at this time. The likely attack vector requires authenticated use of the Block Editor; attackers must have contributor or higher permissions to add or edit blocks. Once malicious content is stored, any user who views the page can be affected.

Generated by OpenCVE AI on May 14, 2026 at 08:20 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to Meta Field Block plugin version 1.5.3 or later, which removes the insecure handling of the 'tagName' attribute.
  • If an upgrade cannot be performed immediately, delete any blocks that include custom tag names or remove the plugin entirely until a fix becomes available.
  • Restrict contributor and higher roles from editing blocks or enforce stricter content moderation to prevent injection of malicious tags.

Generated by OpenCVE AI on May 14, 2026 at 08:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 14 May 2026 07:00:00 +0000

Type Values Removed Values Added
Description 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.
Title Meta Field Block <= 1.5.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'tagName' Block Attribute
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 6.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-05-14T06:44:13.636Z

Reserved: 2026-04-13T19:24:45.285Z

Link: CVE-2026-6252

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-05-14T07:16:20.513

Modified: 2026-05-14T07:16:20.513

Link: CVE-2026-6252

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-14T08:30:16Z

Weaknesses