HomeWordPress vulnerabilitiesMeta Field Block
Meta Field Block vulnerabilities
Meta Field Block has 2 known vulnerabilities in this database. The most recent published record is dated 28 May 2026.
- Known vulnerabilities
- 2
- Active installs
- 10,000+
- Latest version
- 1.6.0
- Last updated
- 7 Sep 2026
- Most recent
- 28 May 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-3173 | Medium 6.5 | Up to 1.5.1 | Fixed in a later version (latest 1.6.0) | 28 May 2026 |
| Cross-site scripting (XSS) CVE-2026-6252 | Medium 6.4 | Up to 1.5.2 | Fixed in a later version (latest 1.6.0) | 14 May 2026 |
Read the published descriptions
- CVE-2026-3173, 28 May 2026
- 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 record
- CVE-2026-6252, 14 May 2026
- The Meta Field Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'tagName' block attribute in all versions up to, and including, 1.5.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
What to do if you run Meta Field Block
If you run Meta Field Block, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Meta Field Block vulnerabilities
Free. We email you when a new vulnerability is published for Meta Field Block, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.