Description
The GenerateBlocks plugin for WordPress is vulnerable to information exposure due to missing object-level authorization checks in versions up to, and including, 2.1.2. This is due to the plugin registering multiple REST API routes under `generateblocks/v1/meta/` that gate access with `current_user_can('edit_posts')`, which is granted to low-privileged roles such as Contributor. The handlers accept arbitrary entity IDs (user IDs, post IDs, etc.) and meta keys, returning any requested metadata with only a short blacklist of password-like keys for protection. There is no object-level authorization ensuring the caller is requesting only their own data, and there is no allowlist of safe keys. This makes it possible for authenticated attackers, with Contributor-level access and above, to exfiltrate personally identifiable information (PII) and other sensitive profile data of administrator accounts or any other users by directly querying user meta keys via the exposed endpoints via the `get_user_meta_rest` function. In typical WordPress + WooCommerce setups, this includes names, email, phone, and address fields that WooCommerce stores in user meta, enabling targeted phishing, account takeover pretexting, and privacy breaches.
Published: 2025-12-13
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Sensitive Information Disclosure
Action: Patch
AI Analysis

Impact

The vulnerability resides in the GenerateBlocks WordPress plugin, which registers REST API routes that are protected only by a generic capability check for editing posts. User with Contributor level or higher can request arbitrary user or post meta keys, and the plugin does not verify that the requested data belongs to the caller, nor does it enforce a whitelist of safe keys. Consequently, an attacker can retrieve personally identifiable information such as names, email addresses, phone numbers and addresses from WooCommerce user profiles, enabling phishing, account takeover pretexting, and privacy violations.

Affected Systems

Edge22’s GenerateBlocks plugin, versions up to and including 2.1.2, on any WordPress installation. Any site that hosts this plugin and has users with Contributor or higher privileges is exposed.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity, while the EPSS score of less than 1% suggests a low probability of exploitation at this time. The vulnerability is not listed in the CISA KEV catalog, underscoring its relative novelty. The likely attack vector is an authenticated user with Contributor or higher role accessing the REST endpoints, which can be exploited without elevated privileges beyond the granted ‘edit_posts’ capability.

Generated by OpenCVE AI on April 22, 2026 at 00:13 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the GenerateBlocks plugin to a fixed version if available.
  • Revoke or reduce the ‘edit_posts’ capability for Contributor users or remove the Contributor role if it is unnecessary.
  • Restrict REST API exposure by implementing an allow‑list of safe metadata keys or by configuring the WordPress REST API to block unexpected meta queries.
  • After applying the update, perform an audit of the REST endpoints to ensure no sensitive metadata is returned to lower‑privileged users.

Generated by OpenCVE AI on April 22, 2026 at 00:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 15 Dec 2025 16:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sun, 14 Dec 2025 21:30:00 +0000

Type Values Removed Values Added
First Time appeared Edge22
Edge22 generateblocks
Wordpress
Wordpress wordpress
Vendors & Products Edge22
Edge22 generateblocks
Wordpress
Wordpress wordpress

Sat, 13 Dec 2025 03:45:00 +0000

Type Values Removed Values Added
Description The GenerateBlocks plugin for WordPress is vulnerable to information exposure due to missing object-level authorization checks in versions up to, and including, 2.1.2. This is due to the plugin registering multiple REST API routes under `generateblocks/v1/meta/` that gate access with `current_user_can('edit_posts')`, which is granted to low-privileged roles such as Contributor. The handlers accept arbitrary entity IDs (user IDs, post IDs, etc.) and meta keys, returning any requested metadata with only a short blacklist of password-like keys for protection. There is no object-level authorization ensuring the caller is requesting only their own data, and there is no allowlist of safe keys. This makes it possible for authenticated attackers, with Contributor-level access and above, to exfiltrate personally identifiable information (PII) and other sensitive profile data of administrator accounts or any other users by directly querying user meta keys via the exposed endpoints via the `get_user_meta_rest` function. In typical WordPress + WooCommerce setups, this includes names, email, phone, and address fields that WooCommerce stores in user meta, enabling targeted phishing, account takeover pretexting, and privacy breaches.
Title GenerateBlocks <= 2.1.2 - Authenticated (Contributor+) Information Exposure via Metadata
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}


Subscriptions

Edge22 Generateblocks
Wordpress Wordpress
cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-04-08T16:58:56.050Z

Reserved: 2025-10-30T15:01:41.942Z

Link: CVE-2025-12512

cve-icon Vulnrichment

Updated: 2025-12-15T15:44:00.401Z

cve-icon NVD

Status : Deferred

Published: 2025-12-13T16:16:46.530

Modified: 2026-04-15T00:35:42.020

Link: CVE-2025-12512

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-22T00:15:03Z

Weaknesses