coblocks vulnerabilities and fixes
Recent CVEs affecting coblocks, with upgrade or downgrade steps. 4 tracked.
coblocks has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2024-08-29. Highest priority: CVE-2024-4260 (score 39/100).
- CVE-2024-7132 MEDIUM 4.8 UPGRADE The Page Builder Gutenberg Blocks WordPress plugin before 3.1.13 does not escape the content of post embed vi
- CVE-2024-4260 MEDIUM 6.5 UPGRADE The Page Builder Gutenberg Blocks WordPress plugin before 3.1.12 does not prevent users from pinging arbitrar
- CVE-2024-2369 MEDIUM 5.4 UPGRADE The Page Builder Gutenberg Blocks WordPress plugin before 3.1.7 does not validate and escape some of its block
- CVE-2024-1049 MEDIUM 6.4 UPGRADE The Page Builder Gutenberg Blocks – CoBlocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting
FAQ
How do I fix coblocks 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 coblocks being exploited right now?
None of the tracked coblocks CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which coblocks CVE should I patch first?
CVE-2024-4260 currently ranks highest (39/100): The Page Builder Gutenberg Blocks WordPress plugin before 3.1.12 does not prevent users from pinging arbitrar.