Approved changes feed: RSS · Atom

cpe:2.3:a:creativethemeshq:blocksy:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorCreativethemeshq (bd14713a-5a3c-56cf-bdfb-78591998855f)
ProductBlocksy (7fdaedb9-9a67-53b8-bbf6-c83e2b1d6f6b)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-8365 vulnerable 2026-07-29 01:09:05.800335 Blocksy <= 2.1.41 - Authenticated (Contributor+) PHP Object Injection via Deserialization of Untrusted Data via 'blocksy_meta' REST API Field
HIGH (8.8)
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().
Published: 2026-06-09T08:29:40.638Z
Updated: 2026-06-09T12:56:15.813Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-2583 vulnerable 2026-06-08 07:55:17.252388 Blocksy <= 2.1.30 - Authenticated (Contributor+) Stored Cross-Site Scripting via `blocksy_meta` Fields
MEDIUM (6.4)
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.
Published: 2026-03-02T22:23:39.951Z
Updated: 2026-04-08T17:24:26.380Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-55713 vulnerable 2026-06-08 07:33:15.281679 WordPress Blocksy Theme <= 2.1.6 - Cross Site Scripting (XSS) Vulnerability
MEDIUM (5.9)
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.
Published: 2025-08-14T18:21:25.460Z
Updated: 2026-04-28T16:13:37.517Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-47465 vulnerable 2026-06-08 07:27:14.426884 WordPress Blocksy theme <= 2.0.97 - Broken Access Control Vulnerability
MEDIUM (4.9)
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.
Published: 2025-05-07T14:19:41.065Z
Updated: 2026-04-28T16:12:42.018Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-5439 vulnerable 2026-06-08 06:56:16.023741 Blocksy <= 2.0.50 - Authenticated (Contributor+) Stored Cross-Site Scripting
MEDIUM (6.4)
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.
Published: 2024-06-05T07:34:56.901Z
Updated: 2026-04-08T17:19:37.421Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-4943 vulnerable 2026-06-08 06:50:19.078806 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-4158 vulnerable 2026-06-08 06:50:17.125446 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-3747 vulnerable 2026-06-08 06:43:51.368891 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-37469 vulnerable 2026-06-08 06:39:47.653936 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-32961 vulnerable 2026-06-08 06:37:24.790162 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-31382 vulnerable 2026-06-08 06:35:31.394747 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-24871 vulnerable 2026-06-08 06:29:41.943559 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-1767 vulnerable 2026-06-08 06:27:14.443535 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-11420 vulnerable 2026-06-08 06:23:49.619407 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.