Creativethemes
Creativethemes Blocksy: vulnerabilities and CVEs
Creativethemes Blocksy has 14 published vulnerabilities, 2 of them in the last 12 months. 0 are rated critical and 0 are listed by CISA as actively exploited.
CVEs14
Last 12 months2
Critical0
Actively exploited0
All vulnerabilities in the catalogue →⭐ Follow this technology
Latest vulnerabilities
| CVE | Severity | EPSS | Active exploitation | Published | Description |
|---|---|---|---|---|---|
| CVE-2026-8365 | High (8.8) | 1.6% | — | Jun 9, 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… |
| CVE-2026-2583 | Medium (6.4) | 0.27% | — | Mar 2, 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… |
| CVE-2025-55713 | Medium (5.9) | 0.18% | — | Aug 14, 2025 | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in creativethemeshq Blocksy blocksy allows Stored XSS.This issue affects Blocksy: from n/a through <= 2.1.6. |
| CVE-2025-47465 | Medium (4.9) | 0.38% | — | May 7, 2025 | Missing Authorization vulnerability in creativethemeshq Blocksy blocksy allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Blocksy: from n/a through <= 2.0.97. |
| CVE-2024-37469 | High (8.8) | 0.19% | — | Jan 2, 2025 | Cross-Site Request Forgery (CSRF) vulnerability in creativethemeshq Blocksy blocksy allows Cross Site Request Forgery.This issue affects Blocksy: from n/a through <= 2.0.22. |
| CVE-2024-11420 | Medium (5.4) | 0.26% | — | Dec 5, 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… |
| CVE-2024-5439 | Medium (5.4) | 0.29% | — | Jun 5, 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… |
| CVE-2024-4943 | Medium (5.4) | 0.26% | — | May 21, 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… |
| CVE-2024-4158 | Medium (5.4) | 0.34% | — | May 14, 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… |
| CVE-2024-3747 | Medium (5.4) | 0.42% | — | May 2, 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… |
| CVE-2024-32961 | Medium (5.4) | 0.32% | — | Apr 25, 2024 | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in creativethemeshq Blocksy blocksy.This issue affects Blocksy: from n/a through <= 2.0.33. |
| CVE-2024-31382 | High (8.8) | 0.23% | — | Apr 15, 2024 | Cross-Site Request Forgery (CSRF) vulnerability in creativethemeshq Blocksy blocksy.This issue affects Blocksy: from n/a through <= 2.0.22. |
| CVE-2024-1767 | Medium (5.4) | 0.32% | — | Mar 9, 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… |
| CVE-2024-24871 | Medium (5.4) | 0.32% | — | Feb 8, 2024 | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in creativethemeshq Blocksy blocksy.This issue affects Blocksy: from n/a through <= 2.0.19. |