Meta Field Block <= 1.5.1 - Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary User Meta Exposure
| CVE | CVE-2026-3173 |
|---|---|
| CVSS | 6.5 (Medium) |
| Publicly Published | May 27, 2026 |
| Last Updated | May 28, 2026 |
| Researcher |
Osvaldo Noe Gonzalez Del Rio (Os)
- krei.dev | ogbuilders.io
|
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.
References
Share
Vulnerability Details for Meta Field Block – Display custom fields in the Block Editor without coding
| Software Type | Plugin |
|---|---|
| Software Slug | display-a-meta-field-as-block (view on wordpress.org) |
| Patched? | Yes |
| Remediation | Update to version 1.5.2, or a newer patched version |
| Affected Version |
|
| Patched Version |
|
Recent vulnerabilities in Meta Field Block – Display custom fields in the Block Editor without coding
| # | Title | CVE ID | CVSS | Researchers | Date |
|---|---|---|---|---|---|
| 1 | Meta Field Block <= 1.5.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'tagName' Block Attribute | CVE-2026-6252 | Muhammad Yudha - DJ | May 13, 2026 | |
| 2 | Freemius <= 2.10.1 - Reflected DOM-Based Cross-Site Scripting via url Parameter | CVE-2024-13362 | Asaf Mozes | April 30, 2026 | |
| 3 | Meta Field Block <= 1.2.13 - Authenticated (Contributor+) Stored Cross-Site Scripting | CVE-2024-43278 | Ngô Thiên An (ancorn_) | August 16, 2024 |
This record contains material that is subject to copyright.
Copyright 2012-2026 Defiant Inc.
License: Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy. Read more.
Copyright 1999-2026 The MITRE Corporation
License: CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy. Read more.
Have information to add, or spot any errors? Contact us at wfi-support@wordfence.com so we can make any appropriate adjustments.
Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!
Learn moreWant to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.
The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.
Documentation