CVE-2024-23500
📋 TL;DR
This Server-Side Request Forgery (SSRF) vulnerability in Kadence WP Gutenberg Blocks allows attackers to make unauthorized requests from the WordPress server to internal or external systems. It affects WordPress sites using the Kadence Blocks plugin from any version up to 3.2.19.
💻 Affected Systems
- Kadence WP Gutenberg Blocks (Kadence Blocks)
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Attackers could access internal services, exfiltrate sensitive data, perform port scanning, or chain with other vulnerabilities to achieve remote code execution.
Likely Case
Information disclosure from internal services, scanning of internal networks, or making requests to cloud metadata services to obtain credentials.
If Mitigated
Limited impact if network segmentation restricts internal access and external requests are filtered.
🎯 Exploit Status
SSRF vulnerabilities typically require some level of user interaction or specific plugin functionality to trigger.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 3.2.20 or later
Vendor Advisory: https://patchstack.com/database/vulnerability/kadence-blocks/wordpress-kadence-blocks-plugin-3-2-19-server-side-request-forgery-ssrf-vulnerability
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'Kadence Blocks' and click 'Update Now'. 4. Alternatively, download version 3.2.20+ from WordPress.org and manually update.
🔧 Temporary Workarounds
Disable vulnerable functionality
allIdentify and disable the specific Kadence Blocks feature causing the SSRF if not essential
Network restrictions
linuxImplement outbound firewall rules to restrict WordPress server from accessing internal services
iptables -A OUTPUT -p tcp --dport 80 -j DROP
iptables -A OUTPUT -p tcp --dport 443 -j DROP
🧯 If You Can't Patch
- Disable Kadence Blocks plugin completely until patched
- Implement web application firewall (WAF) rules to block SSRF patterns
🔍 How to Verify
Check if Vulnerable:
Check WordPress admin > Plugins > Installed Plugins for Kadence Blocks version. If version is 3.2.19 or lower, you are vulnerable.
Check Version:
wp plugin list --name=kadence-blocks --field=version (if WP-CLI installed)
Verify Fix Applied:
After updating, verify Kadence Blocks version shows 3.2.20 or higher in WordPress plugins list.
📡 Detection & Monitoring
Log Indicators:
- Unusual outbound HTTP requests from WordPress server
- Requests to internal IP addresses or localhost
- Multiple rapid requests to different endpoints
Network Indicators:
- WordPress server making unexpected outbound connections
- Requests to cloud metadata services (169.254.169.254)
- Port scanning patterns from WordPress server
SIEM Query:
source="wordpress.logs" AND (url CONTAINS "localhost" OR url CONTAINS "127.0.0.1" OR url CONTAINS "169.254.169.254" OR url CONTAINS "internal")
🔗 References
- https://patchstack.com/database/vulnerability/kadence-blocks/wordpress-kadence-blocks-plugin-3-2-19-server-side-request-forgery-ssrf-vulnerability?_s_id=cve
- https://patchstack.com/database/vulnerability/kadence-blocks/wordpress-kadence-blocks-plugin-3-2-19-server-side-request-forgery-ssrf-vulnerability?_s_id=cve