{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3173 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3173 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-3173 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-3173 in the wild and no public exploit code.\n\nAffected product: mr2p Meta Field Block – Display custom fields in the Block Editor without coding. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3173/ (Markdown: https://insights.sbomify.com/CVE-2026-3173/index.md)","id":"CVE-2026-3173","markdown":"https://insights.sbomify.com/CVE-2026-3173/index.md","name":"CVE-2026-3173","record":{"aliases":["GHSA-2xg8-969f-84gv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can read arbitrary user, post, and term metadata, potentially exposing sensitive PII due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in Meta Field Block – Display custom fields in the Block Editor without coding","id":"CVE-2026-3173","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Event Tickets and Registration \u003c= 5.27.4 - Missing Authorization to Unauthenticated Stripe Credentials Update","id":"CVE-2026-3174"},"packages":[],"prev":{"headline":"pgvector buffer overflow in parallel HNSW index build","id":"CVE-2026-3172"},"products":["Meta Field Block – Display custom fields in the Block Editor without coding"],"published":"2026-05-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["mr2p"]},"summary":"Authenticated contributors can read arbitrary user, post, and term metadata, potentially exposing sensitive PII due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2026-3173/"}