Blocksy: known security problems
14 known security problems reported for this WordPress theme, with the affected versions, the fix and what to do.
Updated
In short
There are 14 known security problems on this page. Each one has a fixed version. Updating to version 2.1.42 or newer covers every fixed problem listed here.
Based on public reports. Check the theme’s changelog. Watchfox AI may be wrong.
Get an email when your site is affected: install Watchfox AI (free)
Someone with a contributor account on your site could in some setups, take over your site
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.1.41
- Fixed in
- 2.1.42
- What to do
- If your site has an affected version, update Blocksy to version 2.1.42 or newer.
- Official ID
- CVE-2026-8365
- Report title
- Blocksy <= 2.1.41 - Authenticated (Contributor+) PHP Object Injection via Deserialization of Untrusted Data via 'blocksy_meta' REST API Field
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could plant harmful code that runs for your visitors or admins (up to and including 2.1.30)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.1.30
- Fixed in
- 2.1.31
- What to do
- If your site has an affected version, update Blocksy to version 2.1.31 or newer.
- Official ID
- CVE-2026-2583
- Report title
- Blocksy <= 2.1.30 - Authenticated (Contributor+) Stored Cross-Site Scripting via `blocksy_meta` Fields
- First reported
- Sources
- Wordfence, seen
Someone with a shop manager account on your site could plant harmful code that runs for your visitors or admins
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.1.6
- Fixed in
- 2.1.7
- What to do
- If your site has an affected version, update Blocksy to version 2.1.7 or newer.
- Official ID
- CVE-2025-55713
- Report title
- Blocksy <= 2.1.6 - Authenticated (Shop manager+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone could do things on your site they should not be allowed to
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.97
- Fixed in
- 2.0.98
- What to do
- If your site has an affected version, update Blocksy to version 2.0.98 or newer.
- Official ID
- CVE-2025-47465
- Report title
- Blocksy <= 2.0.97 - Missing Authorization
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could plant harmful code that runs for your visitors or admins (up to and including 2.0.77)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.77
- Fixed in
- 2.0.78
- What to do
- If your site has an affected version, update Blocksy to version 2.0.78 or newer.
- Official ID
- CVE-2024-11420
- Report title
- Blocksy <= 2.0.77 - Authenticated (Contributor+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone could trick a logged-in admin into changing settings without knowing (up to and including 2.0.22)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.22
- Fixed in
- 2.0.23
- What to do
- If your site has an affected version, update Blocksy to version 2.0.23 or newer.
- Official ID
- CVE-2024-37469
- Report title
- Blocksy <= 2.0.22 - Cross-Site Request Forgery
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could plant harmful code that runs for your visitors or admins (up to and including 2.0.50)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.50
- Fixed in
- 2.0.51
- What to do
- If your site has an affected version, update Blocksy to version 2.0.51 or newer.
- Official ID
- CVE-2024-5439
- Report title
- Blocksy <= 2.0.50 - Authenticated (Contributor+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could plant harmful code that runs for your visitors or admins (up to and including 2.0.46)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.46
- Fixed in
- 2.0.47
- What to do
- If your site has an affected version, update Blocksy to version 2.0.47 or newer.
- Official ID
- CVE-2024-4943
- Report title
- Blocksy <= 2.0.46 - Authenticated (Contributor+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could plant harmful code that runs for your visitors or admins (up to and including 2.0.42)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.42
- Fixed in
- 2.0.43
- What to do
- If your site has an affected version, update Blocksy to version 2.0.43 or newer.
- Official ID
- CVE-2024-4158
- Report title
- Blocksy <= 2.0.42 - Authenticated (Contributor+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could plant harmful code that runs for your visitors or admins (up to and including 2.0.39)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.39
- Fixed in
- 2.0.40
- What to do
- If your site has an affected version, update Blocksy to version 2.0.40 or newer.
- Official ID
- CVE-2024-3747
- Report title
- Blocksy <= 2.0.39 - Authenticated (Contributor+) Stored Cross-Site Scripting via About Me block
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could plant harmful code that runs for your visitors or admins (up to and including 2.0.33)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.33
- Fixed in
- 2.0.34
- What to do
- If your site has an affected version, update Blocksy to version 2.0.34 or newer.
- Official ID
- CVE-2024-32961
- Report title
- Blocksy <= 2.0.33 - Authenticated (Contributor+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone could trick a logged-in admin into changing settings without knowing (up to and including 2.0.22) (2)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.22
- Fixed in
- 2.0.23
- What to do
- If your site has an affected version, update Blocksy to version 2.0.23 or newer.
- Official ID
- CVE-2024-31382
- Report title
- Blocksy <= 2.0.22 - Cross-Site Request Forgery to Notice Dismissal
- First reported
- Sources
- Wordfence, seen
Someone with a contributor account on your site could plant harmful code that runs for your visitors or admins (up to and including 2.0.26)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.26
- Fixed in
- 2.0.27
- What to do
- If your site has an affected version, update Blocksy to version 2.0.27 or newer.
- Official ID
- CVE-2024-1767
- Report title
- Blocksy <= 2.0.26 - Authenticated (Contributor+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Someone with an editor account on your site could plant harmful code that runs for your visitors or admins
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.0.19
- Fixed in
- 2.0.20
- What to do
- If your site has an affected version, update Blocksy to version 2.0.20 or newer.
- Official ID
- CVE-2024-24871
- Report title
- Blocksy <= 2.0.19 - Authenticated (Editor+) Stored Cross-Site Scripting
- First reported
- Sources
- Wordfence, seen
Where this comes from
We collect these reports from public security sources and rewrite them in plain words. Each problem shows its sources and the date we first saw it. This page never says whether your own site is affected: only a check of your site’s versions can tell.
Get an email when your site is affected.
Install Watchfox AI once. It checks your plugins and themes against this list every day, for free.
Install Watchfox AI (free)