WordPress security changelog
MEDIUM CVE-2026-3173 Deferred

Meta Field Block – Display custom fields in the Block Editor without coding: A security weakness

Meta Field Block – Display custom fields in the Block Editor without coding is affected by a security weakness. Exploitation requires at least contributor-level access. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 1.5.1.

CVE / CNA score 6.5 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
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
> 1.5.1
Published
May 28, 2026
Weakness
CWE-639 — Authorization Bypass Through User-Controlled Key

This CVE was published May 28, 2026 and is one of 2 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Meta Field Block – Display custom fields in the Block Editor without coding to a release after 1.5.1, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

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.

Source record

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

References

Primary and upstream sources