CVE-2025-12512: GenerateBlocks <= 2.1.2 - Authenticated (Contributor+) Information Exposure via Metadata
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 currentusercan('editposts'), 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 getusermetarest 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-12512?
CVE-2025-12512 has been assigned a severity rating that indicates it poses a risk of information exposure due to missing authorization checks.
How do I fix CVE-2025-12512?
To fix CVE-2025-12512, update the GenerateBlocks plugin to version 2.1.3 or later.
What kind of data is exposed in CVE-2025-12512?
CVE-2025-12512 can lead to unauthorized access to potentially sensitive information via exposed REST API endpoints.
Which versions of the GenerateBlocks plugin are affected by CVE-2025-12512?
CVE-2025-12512 affects all versions of the GenerateBlocks plugin up to and including 2.1.2.
Is there a recommendation for using GenerateBlocks after CVE-2025-12512?
After addressing CVE-2025-12512, it is recommended to continuously monitor for subsequent updates and security patches for the GenerateBlocks plugin.