HomeWordPress vulnerabilitiesaBlocks
aBlocks vulnerabilities
aBlocks has 2 known vulnerabilities in this database. The most recent published record is dated 7 Jan 2026.
- Known vulnerabilities
- 2
- Active installs
- 2,000+
- Latest version
- 2.14.0
- Last updated
- 24 Sep 2026
- Most recent
- 7 Jan 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 |
|---|---|---|---|---|
| Broken access control CVE-2025-12449 | Medium 5.4 | Up to 2.4.0 | Fixed in a later version (latest 2.14.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-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.