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().
CVE-2026-8365
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EPSS
- 53.7%
- KEV
- Not listed
Published
June 9, 2026
Last Modified
June 9, 2026
References (13)
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/2.1.35/admin/helpers/meta-boxes.php#L104
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/2.1.35/admin/helpers/validator.php#L75
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/2.1.35/inc/classes/db-versioning/utils/db-search-replacer.php#L98
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/2.1.35/inc/classes/raii.php#L12
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/2.1.41/admin/helpers/meta-boxes.php#L104
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/2.1.41/admin/helpers/validator.php#L75
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/2.1.41/inc/classes/db-versioning/utils/db-search-replacer.php#L98
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/2.1.41/inc/classes/raii.php#L12
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/trunk/admin/helpers/meta-boxes.php#L104
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/trunk/admin/helpers/validator.php#L75
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/trunk/inc/classes/db-versioning/utils/db-search-replacer.php#L98
- security@wordfencehttps://themes.trac.wordpress.org/browser/blocksy/trunk/inc/classes/raii.php#L12
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/fd216743-ce8d-4632-9fd1-d63502c2dfcd?source=cve
Vendor Advisories for CVE-2026-8365(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 30× in last 7d / 129× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 129 total refreshes for this CVE.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 17:01 UTCEG score recompute
- 2026-07-05 17:01 UTCGHSA enrichment
- 2026-07-05 03:26 UTCEG score recompute
- 2026-07-05 03:26 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 14:27 UTCEG score recompute
- 2026-07-04 14:27 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 22:55 UTCEG score recompute
- 2026-07-03 22:54 UTCGHSA enrichment
- 2026-07-03 09:36 UTCEG score recompute
- 2026-07-03 09:36 UTCGHSA enrichment
- 2026-07-02 20:36 UTCEG score recompute
- 2026-07-02 20:36 UTCGHSA enrichment
- 2026-07-02 07:36 UTCEG score recompute
- 2026-07-02 07:36 UTCGHSA enrichment
- 2026-07-01 18:35 UTCEG score recompute
- 2026-07-01 18:35 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-01 05:37 UTCEG score recompute
- 2026-07-01 05:36 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 15:40 UTCEG score recompute
- 2026-06-30 15:39 UTCGHSA enrichment
- 2026-06-30 00:18 UTCEG score recompute
- 2026-06-30 00:18 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 11:19 UTCEG score recompute
- 2026-06-29 11:19 UTCGHSA enrichment
- 2026-06-28 22:20 UTCEG score recompute
- 2026-06-28 22:20 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 09:20 UTCEG score recompute
- 2026-06-28 09:20 UTCGHSA enrichment
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 20:19 UTCEG score recompute
- 2026-06-27 20:19 UTCGHSA enrichment
- 2026-06-27 07:20 UTCEG score recompute
- 2026-06-27 07:20 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 18:21 UTCEG score recompute
- 2026-06-26 18:21 UTCGHSA enrichment
- 2026-06-26 05:10 UTCEG score recompute
- 2026-06-26 05:10 UTCGHSA enrichment
- 2026-06-25 16:11 UTCEG score recompute
- 2026-06-25 16:11 UTCGHSA enrichment
- 2026-06-25 13:50 UTCEPSS rescore
- 2026-06-25 03:11 UTCEG score recompute
- 2026-06-25 03:11 UTCGHSA enrichment
- 2026-06-24 14:12 UTCEG score recompute
- 2026-06-24 14:11 UTCGHSA enrichment
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 01:12 UTCEG score recompute
- 2026-06-24 01:12 UTCGHSA enrichment
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 12:11 UTCEG score recompute
- 2026-06-23 12:10 UTCGHSA enrichment
- 2026-06-22 22:31 UTCEG score recompute
- 2026-06-22 22:31 UTCGHSA enrichment
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 05:24 UTCEG score recompute
- 2026-06-22 05:24 UTCGHSA enrichment
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 10:43 UTCEG score recompute
- 2026-06-21 10:43 UTCGHSA enrichment
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-20 21:43 UTCEG score recompute
- 2026-06-20 21:43 UTCGHSA enrichment
- 2026-06-20 07:48 UTCEG score recompute
- 2026-06-20 07:48 UTCGHSA enrichment
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 18:30 UTCEG score recompute
- 2026-06-19 18:30 UTCGHSA enrichment
- 2026-06-19 03:07 UTCEG score recompute
- 2026-06-19 03:07 UTCGHSA enrichment
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 14:04 UTCEG score recompute
- 2026-06-18 14:04 UTCGHSA enrichment
- 2026-06-18 01:01 UTCEG score recompute
- 2026-06-18 01:01 UTCGHSA enrichment
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 11:52 UTCEG score recompute
- 2026-06-17 11:52 UTCGHSA enrichment
- 2026-06-16 22:54 UTCEG score recompute
- 2026-06-16 22:53 UTCGHSA enrichment
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-16 09:54 UTCEG score recompute
- 2026-06-16 09:54 UTCGHSA enrichment
- 2026-06-15 20:55 UTCEG score recompute
- 2026-06-15 20:55 UTCGHSA enrichment
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 07:47 UTCEG score recompute
- 2026-06-15 07:47 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-20208EG 9.8CRITICAL
- CVE-2017-20207EG 9.8CRITICAL
- CVE-2017-20206EG 9.8CRITICAL
- CVE-2017-20189EG 9.8CRITICAL
- CVE-2017-10992EG 9.8EPSS 95%CRITICAL
- CVE-2013-4521EG 9.8EPSS 90%CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS 98%CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-18605EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-8365?
When was CVE-2026-8365 disclosed?
Is CVE-2026-8365 actively exploited?
What is the CVSS score of CVE-2026-8365?
How do I remediate CVE-2026-8365?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-8365
Is Your Infrastructure Affected by CVE-2026-8365?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.