CVE-2026-3173 Missing authorization in Meta Field Block – Display custom fields in the Block Editor without coding
Authenticated contributors can read arbitrary user, post, and term metadata, potentially exposing sensitive PII due to missing authorization checks.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-3173?
CVE-2026-3173 is a medium-severity missing authorization vulnerability in mr2p Meta Field Block – Display custom fields in the Block Editor without coding, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-639
Which versions are affected by CVE-2026-3173?
How do I fix CVE-2026-3173?
No fix has been published for CVE-2026-3173 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-3173 being exploited?
There is no known exploitation of CVE-2026-3173 in the wild and no public exploit code.
Sources
Also known as GHSA-2xg8-969f-84gv.