HomeWordPress vulnerabilitiesGenerateBlocks
GenerateBlocks vulnerabilities
GenerateBlocks has 8 known vulnerabilities in this database. The most recent published record is dated 1 Aug 2026.
- Known vulnerabilities
- 8
- Active installs
- 200,000+
- Latest version
- 2.4.1
- Last updated
- 18 Aug 2026
- Most recent
- 1 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-13458 | Medium 6.4 | Up to 2.3.0 | Fixed in a later version (latest 2.4.1) | 1 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-9756 | Medium 6.4 | Up to 2.2.1 | Fixed in a later version (latest 2.4.1) | 3 Jul 2026 |
| Broken access control CVE-2026-3454 | Medium 6.5 | Up to 2.2.0 | Fixed in a later version (latest 2.4.1) | 5 May 2026 |
| Authentication bypass CVE-2025-12512 | Medium 4.3 | Up to 2.1.2 | Fixed in a later version (latest 2.4.1) | 13 Dec 2025 |
| Broken access control CVE-2025-11879 | Medium 6.5 | Up to 2.1.1 | Fixed in a later version (latest 2.4.1) | 25 Oct 2025 |
| Sensitive data exposure CVE-2024-13546 | Medium 4.3 | Up to 1.9.1 | Fixed in a later version (latest 2.4.1) | 1 Mar 2025 |
| Sensitive data exposure CVE-2024-1452 | Medium 4.3 | Before 1.8.3 | Fixed in 1.8.3 | 13 Mar 2024 |
| Cross-site scripting (XSS) CVE-2021-24751 | Medium 5.4 | Before 1.4.0 | Fixed in 1.4.0 | 29 Nov 2021 |
Read the published descriptions
- CVE-2026-13458, 1 Aug 2026
- The GenerateBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Dynamic Tag Injection in HTML Attributes in all versions up to, and including, 2.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A Contributor-level attacker can store the malicious payload by placing a dynamic tag such as {{post_meta key:...}} in a non-URL HTML attribute (e.g., title, aria-label, alt, or data-* attributes) of a GenerateBlocks element block, then setting the corresponding unprotected post meta key via the Custom Fields metabox to a value containing a closing quote and an injected event-handler attribute. CVE record
- CVE-2026-9756, 3 Jul 2026
- The GenerateBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Headline Block 'linkMetaFieldType' Dynamic Link Attribute in all versions up to, and including, 2.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A contributor-level attacker can store a JavaScript payload in their own profile description (allowlisted by get_safe_user_meta_keys()) and prepend 'javascript:' via the linkMetaFieldType attribute, creating a fully attacker-controlled href that executes when any user, including an administrator, clicks the rendered headline link. CVE record
- CVE-2026-3454, 5 May 2026
- The GenerateBlocks plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2.0. This is due to missing object-level authorization checks in the /wp-json/generateblocks/v1/dynamic-tag-replacements REST endpoint. The endpoint only verifies that the user has the edit_posts capability but does not verify the user has permission to access the specific post or its associated data referenced by attacker-controlled id parameters in dynamic tag content. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive information from arbitrary posts including author email addresses and non-protected post meta values by crafting dynamic tag payloads such as {{post_meta id:<target>|key:<meta_key>}} and {{post_title id:<target>|link:author_email}}. CVE record
- CVE-2025-12512, 13 Dec 2025
- 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. CVE record
- CVE-2025-11879, 25 Oct 2025
- 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. CVE record
- CVE-2024-13546, 1 Mar 2025
- 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. CVE record
- CVE-2024-1452, 13 Mar 2024
- 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. CVE record
- CVE-2021-24751, 29 Nov 2021
- 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. CVE record
What to do if you run GenerateBlocks
If you run GenerateBlocks, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new GenerateBlocks vulnerabilities
Free. We email you when a new vulnerability is published for GenerateBlocks, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.