Meta Field Block – Display custom fields in the Block Editor without coding: Cross-site scripting
Meta Field Block – Display custom fields in the Block Editor without coding is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 1.5.2.
- Component
- Meta Field Block – Display custom fields in the Block Editor without coding
- Plugin slug
meta-field-block- Affected
- <= 1.5.2
- Safe version
- See mitigation notes
- Published
- May 14, 2026
This CVE was published May 14, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
No fixed release is identified. Update Meta Field Block – Display custom fields in the Block Editor without coding when a release after 1.5.2 becomes available; until then, disable and remove it when the site's risk warrants.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N