HomeWordPress vulnerabilitiesaBlocks
aBlocks vulnerabilities
aBlocks has 7 known vulnerabilities in this database. The most recent published record is dated 7 Nov 2026.
- Known vulnerabilities
- 7
- Active installs
- 2,000+
- Latest version
- 2.20.0
- Last updated
- 5 Nov 2026
- Most recent
- 7 Nov 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-118800 | Medium 6.4 | Up to 2.18.0 | Fixed in a later version (latest 2.20.0) | 7 Nov 2026 |
| Sensitive data exposure CVE-2026-118801 | Medium 4.3 | Up to 2.18.0 | Fixed in a later version (latest 2.20.0) | 7 Nov 2026 |
| Privilege escalation CVE-2026-110018 | High 8.8 | Up to 2.17.0 | Fixed in a later version (latest 2.20.0) | 24 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-40804 | High 7.1 | Up to 2.16.0 | Fixed in a later version (latest 2.20.0) | 8 Oct 2026 |
| Privilege escalation CVE-2026-57386 | High 8.8 | Before 2.9.1 | Fixed in 2.9.1 | 13 Jul 2026 |
| Broken access control CVE-2025-12449 | Medium 5.4 | Up to 2.4.0 | Fixed in a later version (latest 2.20.0) | 7 Jan 2026 |
| Cross-site scripting (XSS) CVE-2024-13465 | Medium 6.4 | Before 1.6.2 | Fixed in 1.6.2 | 18 Feb 2025 |
Read the published descriptions
- CVE-2026-118800, 7 Nov 2026
- The aBlocks - Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'headingTag' parameter in all versions up to, and including, 2.18.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. CVE record
- CVE-2026-118801, 7 Nov 2026
- The aBlocks - Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.18.0 via the 'id' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to extract the full rendered body content of any password-protected post of any post type by embedding the shortcode with the target post's ID. Author-level attackers and above can additionally publish a post embedding the shortcode, exposing the password-protected content to unauthenticated visitors. CVE record
- CVE-2026-110018, 24 Oct 2026
- The aBlocks - Gutenberg Blocks, User Dashboard Builder, Popup Builder, Form Builder & Animation Builder plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.17.0 via the `/ablocks/v1/form-builder/registration` REST endpoint. The vulnerability exists because the endpoint is registered with `permission_callback => __return_true` and the `register()` handler reads `roleSlug` directly from attacker-controlled block attributes in `post_content` without ever verifying that the block's `formType` is `registration` - a condition that `RegistrationFormSanitizer::verify()` imposes only at save-time, meaning a Contributor can preserve an arbitrary `roleSlug` by saving a block with `formType='login'` and then triggering the endpoint via a valid `wp_rest` nonce and post-ownership check. This makes it possible for authenticated attackers, with Contributor-level access and above, to escalate their WordPress role to Editor or any other non-administrator role and receive a fully authenticated session at the elevated privilege level via `WP_User::set_role()` and `wp_set_auth_cookie()`. Escalation is bounded below administrator-tier roles because `is_safe_registration_role()` rejects any role holding `manage_options`, `edit_users`, `delete_users`, `create_users`, `promote_users`, or `edit_theme_options`, meaning the highest practically reachable role on a standard WordPress installation is Editor. CVE record
- CVE-2026-40804, 8 Oct 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Kodezen LLC aBlocks ablocks allows Reflected XSS.This issue affects aBlocks: from n/a through 2.16.0. CVE record
- CVE-2026-57386, 13 Jul 2026
- Incorrect Privilege Assignment vulnerability in Kodezen LLC aBlocks ablocks allows Privilege Escalation.This issue affects aBlocks: from n/a before 2.9.1. CVE record
- CVE-2025-12449, 7 Jan 2026
- The aBlocks - WordPress Gutenberg Blocks plugin for WordPress is vulnerable to unauthorized modification of data and disclosure of sensitive information due to missing capability checks on multiple AJAX actions in all versions up to, and including, 2.4.0. This makes it possible for authenticated attackers, with subscriber level access and above, to read plugin settings including block visibility, maintenance mode configuration, and third-party email marketing API keys, as well as read sensitive configuration data including API keys for email marketing services. CVE record
- CVE-2024-13465, 18 Feb 2025
- The aBlocks - WordPress Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the "Table Of Content" Block, specifically in the "markerView" attribute, in all versions up to, and including, 1.6.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. CVE record
What to do if you run aBlocks
If you run aBlocks, 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 aBlocks vulnerabilities
Free. We email you when a new vulnerability is published for aBlocks, 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.