What the vulnerability does
01Description
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.
Explanation of Vulnerability in Simple Terms
02Summary
Meta Field Block versions up to 1.5.1 contain an authorization flaw that allows authenticated users to read sensitive custom field data they should not access. The vulnerability requires a logged-in account but no special privileges. Site administrators should update to a version newer than 1.5.1 to restrict unauthorized data exposure.
What an attacker can do
03Attacker Capabilities
Read custom field data belonging to other users or restricted content areas.
Potential impact on your site
04Site Impact
Sensitive custom field information may be exposed to any authenticated user, potentially including private user data or confidential post metadata.
Conditions required to exploit
05Prerequisites
Attacker must have a valid user account with login access to the WordPress site.
Key dates
06Disclosure timeline
May 28, 2026
CVE published
May 28, 2026
Record updated
