Vulnerabilities and security researches forgenerateblocks generateblocks

Jun 06, 2024

CVE, Research URL: CVE-2024-1452
Home page URL: Security reports for GenerateBlocks
Application: GenerateBlocks
Date: Mar 13, 2024
Research Description: The GenerateBlocks plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.2 via Query Loop. This makes it possible for authenticated attackers, with contributor access and above, to see contents of posts and pages in draft or private status as well as those with scheduled publication dates.
Affected versions: max 1.8.3.
Status: vulnerable

CVE, Research URL: CVE-2021-24751
Home page URL: Security reports for GenerateBlocks
Application: GenerateBlocks
Date: Nov 29, 2021
Research Description: The GenerateBlocks WordPress plugin before 1.4.0 does not validate the generateblocks/container block's tagName attribute, which could allow users with a role as low as contributor to perform Cross-Site Scripting attacks.
Affected versions: max 1.4.0.
Status: vulnerable

Mar 01, 2025

CVE, Research URL: CVE-2024-13546
Home page URL: Security reports for GenerateBlocks
Application: GenerateBlocks
Date: Mar 01, 2025
Research Description: The GenerateBlocks plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.9.1 via the 'get_image_description' function. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive data including the content of private, draft, and scheduled posts and pages.
Affected versions: max 2.0.0.
Status: vulnerable

Nov 10, 2025

CVE, Research URL: CVE-2025-11879
Home page URL: Security reports for GenerateBlocks
Application: GenerateBlocks
Date: Oct 25, 2025
Research Description: The GenerateBlocks plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'get_option_rest' function in all versions up to, and including, 2.1.1. This makes it possible for authenticated attackers, with contributor level access and above, to read arbitrary WordPress options, including sensitive information such as SMTP credentials, API keys, and other data stored by other plugins.
Affected versions: max 2.1.2.
Status: vulnerable

Jan 08, 2026

CVE, Research URL: CVE-2025-12512
Home page URL: Security reports for GenerateBlocks
Application: GenerateBlocks
Date: Dec 13, 2025
Research 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.
Affected versions: max 2.2.0.
Status: vulnerable