Meta Field Block <= 1.5.1 — Insecure Direct Object Reference to Authenticated (Contributor+) Arbitrary User Meta Exposure
CVE-2026-3173Published · Updated Action summary
Affected: ≤1.5.1Update to 1.5.2 or newer
All remediation steps- Severity
- Medium6.5
- CVSS
- 6.5CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:LPrivileges required- Low
UI:NUser interaction- None
S:UScope- Unchanged
C:HConfidentiality- High
I:NIntegrity- None
A:NAvailability- None
- Required access
- Unknown
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
Meta Field Block – Display Custom Fields for ACF, Meta Box and More display-a-meta-field-as-block
- Affected≤ 1.5.1
- Patched in1.5.2
Update to 1.5.2 or newer.
You are affected if you run ≤ 1.5.1. Version 1.5.2 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Meta Field Block – Display Custom Fields for ACF, Meta Box and More.
- No admin access? Run a passive check of your site. It reads public files only.
What to do
- Update to version 1.5.2, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Meta Field Block – Display Custom Fields for ACF, Meta Box and More to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Osvaldo Noe Gonzalez Del Rio (Os).
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in Meta Field Block – Display Custom Fields for ACF, Meta Box and More
All 4| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.4 | Authenticated (Contributor+) Stored Cross-Site Scripting via 'tagName' Block Attribute ≤1.5.2Update to 1.5.3 | CVE-2026-6252 | |
| Medium6.1 | Reflected DOM-Based Cross-Site Scripting via url Parameter ≤5.5.8Update to 5.5.9 | CVE-2024-13362 | |
| Medium6.4 | Authenticated (Contributor+) Stored Cross-Site Scripting ≤1.2.13Update to 1.2.14 | CVE-2024-43278 |
- Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via 'tagName' Block Attribute
≤1.5.2Update to 1.5.3
- Medium6.1Reflected DOM-Based Cross-Site Scripting via url Parameter
≤5.5.8Update to 5.5.9
- Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤1.2.13Update to 1.2.14
Timeline
CVE published
Severity medium, CVSS 6.5
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.