Meta Field Block – Display custom fields in the Block Editor without coding: Broken access control
Meta Field Block – Display custom fields in the Block Editor without coding is affected by broken access control. Exploitation requires an authenticated contributor account. A successful request can reach data or an operation that should be restricted to another user or a more privileged role. The published affected range is <= 1.5.1.
- Component
- Meta Field Block – Display custom fields in the Block Editor without coding
- Plugin slug
display-a-meta-field-as-block- Affected
- <= 1.5.1
- Safe version
- See mitigation notes
- Published
- May 28, 2026
This CVE was published May 28, 2026 and is one of 2 known issues 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.1 becomes available; until then, disable and remove it when the site's risk warrants. The official upstream changelog lists version 1.5.4, which is newer than the published affected range. Its changelog does not clearly confirm this specific fix, so it is not counted as a known-safe release.
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 Insecure Direct Object Reference in all versions up to, and including, 1.5.1. This is due to the plugin allowing users to specify arbitrary object IDs and object types via block attributes without validating whether the authenticated user has permission to access the requested object's metadata. This makes it possible for authenticated attackers, with Contributor-level access and above, to read arbitrary user meta, post meta, and term meta data from any object in the database. On sites using plugins that store sensitive data in meta fields (e.g., WooCommerce billing/shipping information), this could lead to the exposure of Personally Identifiable Information (PII) including names, email addresses, phone numbers, and physical addresses.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N