Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesBlocksy

Blocksy vulnerabilities

Blocksy has 8 known vulnerabilities in this database. The most recent published record is dated 9 Jun 2026.

Known vulnerabilities
8
Active installs
300,000+
Latest version
2.1.57
Last updated
11 Sep 2026
Most recent
9 Jun 2026

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
Remote code execution
CVE-2026-8365
High 8.8Up to 2.1.35Fixed in a later version (latest 2.1.57)9 Jun 2026
Cross-site scripting (XSS)
CVE-2026-2583
Medium 6.4Up to 2.1.30Fixed in a later version (latest 2.1.57)2 Mar 2026
Cross-site scripting (XSS)
CVE-2024-11420
Medium 6.4Before 2.0.78Fixed in 2.0.785 Dec 2024
Cross-site scripting (XSS)
CVE-2024-5439
Medium 6.4Before 2.0.51Fixed in 2.0.515 Jun 2024
Cross-site scripting (XSS)
CVE-2024-4943
Medium 6.4Before 2.0.47Fixed in 2.0.4721 May 2024
Cross-site scripting (XSS)
CVE-2024-4158
Medium 6.4Before 2.0.43Fixed in 2.0.4314 May 2024
Cross-site scripting (XSS)
CVE-2024-3747
Medium 6.4Before 2.0.40Fixed in 2.0.402 May 2024
Cross-site scripting (XSS)
CVE-2024-1767
Medium 6.4Before 2.0.27Fixed in 2.0.279 Mar 2024
Read the published descriptions
CVE-2026-8365, 9 Jun 2026
The Blocksy theme for WordPress is vulnerable to PHP Object Injection leading to Remote Code Execution via the 'blocksy_meta' REST API field and the V200 database migration in versions up to and including 2.1.35. This is due to insufficient input sanitization in the blocksy_sanitize_post_meta_options() function, which only blocks values containing '<' or '>' and does not prevent serialized PHP object strings from being stored in post meta, combined with the SearchReplacer::run_recursively() function unconditionally deserializing all string values via @unserialize() during migration without restricting allowed classes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject a serialized Blocksy\RaiiPattern object into post meta that, when the V200 migration runs on an upgraded site, is deserialized and triggers RaiiPattern::__destruct(), which executes arbitrary PHP callables via call_user_func(). CVE record
CVE-2026-2583, 2 Mar 2026
The Blocksy theme for WordPress is vulnerable to Stored Cross-Site Scripting via the `blocksy_meta` metadata fields in all versions up to, and including, 2.1.30 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2024-11420, 5 Dec 2024
The Blocksy theme for WordPress is vulnerable to Stored Cross-Site Scripting via the Contact Info Block link parameter in all versions up to, and including, 2.0.77 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2024-5439, 5 Jun 2024
The Blocksy theme for WordPress is vulnerable to Reflected Cross-Site Scripting via the custom_url parameter in all versions up to, and including, 2.0.50 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. CVE record
CVE-2024-4943, 21 May 2024
The Blocksy theme for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘has_field_link_rel’ parameter in all versions up to, and including, 2.0.46 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2024-4158, 14 May 2024
The Blocksy theme for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘tagName’ parameter in versions up to, and including, 2.0.42 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2024-3747, 2 May 2024
The Blocksy theme for WordPress is vulnerable to Stored Cross-Site Scripting via the className parameter in the About Me block in all versions up to, and including, 2.0.39 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
CVE-2024-1767, 9 Mar 2024
The Blocksy theme for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's blocks in all versions up to, and including, 2.0.26 due to insufficient input sanitization and output escaping on user supplied attributes like 'className' and 'radius'. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record

What to do if you run Blocksy

If you run Blocksy, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.

If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.

Email me about new Blocksy vulnerabilities

Free. We email you when a new vulnerability is published for Blocksy, usually within minutes. Confirm by email; unsubscribe any time.

Focus on your business. We’ll take care of your website.

From everyday updates to ongoing care, we keep your website working.

Get website support