Blocksy <= 2.1.41 — Authenticated (Contributor+) PHP Object Injection via Deserialization of Untrusted Data via 'blocksy_meta' REST API Field
CVE-2026-8365Published · Updated Action summary
Affected: ≤2.1.41Update to 2.1.42 or newer
All remediation stepsOn this page3
Overview
- Advisory ID
- CVE-2026-8365
- Product
- Blocksy blocksy
- Affected
- ≤2.1.41
- Fixed in
- 2.1.42
- Weakness
- CWE-502 PHP Object Injection
- Required access
- Low-privilege account (e.g. subscriber)
- Published
- · updated
- Credit
- Quốc Huy (jtwings)
- Source
- Wordfence Intelligence
- Affected≤ 2.1.41
- Patched in2.1.42
Update to 2.1.42 or newer.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:LPrivileges required- Low
UI:NUser interaction- None
S:UScope- Unchanged
C:HConfidentiality- High
I:HIntegrity- High
A:HAvailability- High
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().
Not sure which version you run? Run a passive check — it reads public files only.
Remediation & mitigations
- Update to version 2.1.42, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
References & provenance
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
- 6.4CVE-2026-2583Authenticated (Contributor+) Stored Cross-Site Scripting via blocksy_meta Fields
- 5.5CVE-2025-55713Authenticated (Shop manager+) Stored Cross-Site Scripting
- 2.7CVE-2025-47465Missing Authorization
- 6.4CVE-2024-11420Authenticated (Contributor+) Stored Cross-Site Scripting
- 4.3CVE-2024-37469Cross-Site Request Forgery
Timeline
CVE published
Severity high, CVSS 8.8
Record last updated
Sources & licenses
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.
