Description
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().
References10
- themes.trac.wordpress.org/browser/blocksy/2.1.35/admin/helpers/…
- themes.trac.wordpress.org/browser/blocksy/2.1.35/admin/helpers/…
- themes.trac.wordpress.org/browser/blocksy/2.1.35/inc/classes/db…
- themes.trac.wordpress.org/browser/blocksy/2.1.35/inc/classes/ra…
- themes.trac.wordpress.org/browser/blocksy/2.1.41/admin/helpers/…
- themes.trac.wordpress.org/browser/blocksy/2.1.41/admin/helpers/…
- themes.trac.wordpress.org/browser/blocksy/2.1.41/inc/classes/db…
- themes.trac.wordpress.org/browser/blocksy/2.1.41/inc/classes/ra…
- themes.trac.wordpress.org/browser/blocksy/trunk/admin/helpers/m…
- themes.trac.wordpress.org/browser/blocksy/trunk/admin/helpers/v…
Metrics
- CVSS 3.1
-
8.8
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 67 · as of 15 November 2026
- CWE
- CWE-502
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.