Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

ablocks vulnerabilities and fixes

Recent CVEs affecting ablocks, with upgrade or downgrade steps. 1 tracked.

ablocks has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2025-02-18. Highest priority: CVE-2024-13465 (score 28/100).

FAQ

How do I fix ablocks vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is ablocks being exploited right now?

None of the tracked ablocks CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which ablocks CVE should I patch first?

CVE-2024-13465 currently ranks highest (28/100): The aBlocks – WordPress Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via.

← Back to latest CVEs