CVE-2024-13465
📋 TL;DR
The aBlocks WordPress plugin has a stored XSS vulnerability in its Table Of Content block that allows authenticated attackers with Contributor access or higher to inject malicious scripts. These scripts execute when users view compromised pages, potentially stealing credentials or performing unauthorized actions. All WordPress sites using aBlocks plugin versions up to 1.6.1 are affected.
💻 Affected Systems
- aBlocks – WordPress Gutenberg Blocks
📦 What is this software?
Ablocks by Tusharimran
⚠️ Risk & Real-World Impact
Worst Case
Attackers could steal administrator credentials, install backdoors, redirect users to malicious sites, or deface websites, potentially leading to complete site compromise and data theft.
Likely Case
Attackers with contributor access inject malicious scripts to steal session cookies or user credentials, potentially escalating privileges to gain administrative control of the WordPress site.
If Mitigated
With proper user access controls and content review processes, the impact is limited to potential defacement of individual pages rather than site-wide compromise.
🎯 Exploit Status
Exploitation requires authenticated access with at least Contributor privileges. The vulnerability is in a specific block attribute, making targeted exploitation straightforward for attackers with access.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 1.6.2 or later
Vendor Advisory: https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3236611%40ablocks&new=3236611%40ablocks&sfp_email=&sfph_mail=
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'aBlocks – WordPress Gutenberg Blocks'. 4. Click 'Update Now' if update is available. 5. Alternatively, download version 1.6.2+ from WordPress repository and manually update.
🔧 Temporary Workarounds
Disable aBlocks Plugin
allTemporarily disable the vulnerable plugin until patched
wp plugin deactivate abocks
Restrict Contributor Access
allRemove Contributor role from untrusted users or limit who can create/edit posts
🧯 If You Can't Patch
- Implement strict content review process for all posts/pages created by Contributor-level users
- Install and configure a web application firewall (WAF) with XSS protection rules
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin → Plugins → Installed Plugins → aBlocks version. If version is 1.6.1 or lower, you are vulnerable.Check Version:
wp plugin get abocks --field=versionVerify Fix Applied:
After updating, verify aBlocks plugin shows version 1.6.2 or higher in WordPress admin panel.📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to wp-admin/post.php with markerView parameter containing script tags
- Multiple failed login attempts followed by successful Contributor-level login
Network Indicators:
- Outbound connections to suspicious domains from your WordPress server
- Unexpected JavaScript execution in Table Of Content blocks
SIEM Query:
source="wordpress.log" AND ("markerView" AND ("<script" OR "javascript:"))