blocksy companion vulnerabilities and fixes
Recent CVEs affecting blocksy companion, with upgrade or downgrade steps. 4 tracked.
Also searched as: blocksycompanion.
blocksy companion has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2024-06-03. Highest priority: CVE-2024-4487 (score 32/100).
- CVE-2024-4487 MEDIUM 6.4 UPGRADE The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG uploads in ver
- CVE-2024-35633 MEDIUM 4.4 UPGRADE Server-Side Request Forgery (SSRF) vulnerability in Creative Themes Blocksy Companion blocksy-companion.This i
- CVE-2024-31932 MEDIUM 5.4 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in CreativeThemes Blocksy Companion.This issue affects Blocksy
- CVE-2024-2392 MEDIUM 6.4 UPGRADE The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Newsl
FAQ
How do I fix blocksy companion 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 blocksy companion being exploited right now?
None of the tracked blocksy companion CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which blocksy companion CVE should I patch first?
CVE-2024-4487 currently ranks highest (32/100): The Blocksy Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG uploads in ver.