dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-3173

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Meta Field Block WordPress plugin (versions up to 1.5.1) contains an IDOR vulnerability where block attributes accept arbitrary object IDs and object types without validating user permissions, allowing authenticated Contributors+ to read any user meta, post meta, or term meta from the database.

MitigationUpdate to the latest patched version if available, or disable the plugin. Audit all meta fields storing sensitive data (especially WooCommerce PII) and implement proper capability checks before returning meta data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Meta Field Block plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Meta Field Block' or check wp-content/plugins/ directory for meta-field-block folder
    Affected if Plugin is present and active in the WordPress installation
  2. Check installed plugin version
    In WordPress admin_plugins list, click on Meta Field Block to view version details, or read version from plugin main PHP file header
    Affected if Version is 1.5.1 or below (all versions up to 1.5.1 are affected)
  3. Identify usage of meta field blocks in content
    Search WordPress database or content editor for blocks named 'meta-field-block' or custom meta field blocks in posts, pages, or custom post types
    Affected if Meta field blocks are present and configured to read meta data
  4. Review user role assignments
    Go to Users > All Users in WordPress admin and check for users with Contributor, Author, Editor, or Administrator roles who have access to create/edit content using the plugin
    Affected if Any authenticated user with Contributor+ role exists who could potentially exploit the IDOR
  5. Check meta data accessibility
    Inspect the plugin block attributes configuration - verify if object_id and object_type parameters can be manipulated without validation by attempting to query meta from different object types (user, post, term)
    Affected if Block configuration accepts arbitrary object IDs and types without ownership/permission validation

A user is affected if the Meta Field Block plugin version 1.5.1 or below is active and any Contributor+ role user exists who could exploit the IDOR to read unauthorized meta data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version if available, or disable the plugin. Audit all meta fields storing sensitive data (especially WooCommerce PII) and implement proper capability checks before returning meta data.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version after 1.5.1)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Meta Field Block' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository at wordpress.org/plugins/meta-field-block/ and upload it manually
  6. 6. After updating, verify the plugin is running the latest version in Plugins > Installed Plugins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3173 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3173 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data