Strategic Overview
- Status
- Patched in 2.0.23
- Affected Theme
- Blocksy
- Affected Version
<= 2.0.22- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-37469
At a glance
CVE-2024-37469 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Blocksy WordPress theme, affecting versions <= 2.0.22. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.23; sites on affected versions should update now. Disclosed July 2024, reported by RE-ALTER.
Vulnerability Overview
The Blocksy theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0.22. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Blocksy <= 2.0.22 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Blocksy the fix is 2.0.23: builds <= 2.0.22 are affected, anything from 2.0.23 onward is not.
Remediation
Update to version 2.0.23, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Blocksy: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Blocksy 2.0.23 closes this, and updating the theme is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Blocksy
- 8.8CVE-2026-8365: Blocksy <= 2.1.41 PHP Object Injection
CVE-2026-8365 - 6.4CVE-2026-2583: Blocksy <= 2.1.30 Stored Cross-Site Scripting
CVE-2026-2583 - 6.4CVE-2024-11420: Blocksy <= 2.0.77 Stored Cross-Site Scripting
CVE-2024-11420 - 6.4CVE-2024-5439: Blocksy <= 2.0.50 Stored Cross-Site Scripting
CVE-2024-5439 - 6.4CVE-2024-4943: Blocksy <= 2.0.46 Stored Cross-Site Scripting
CVE-2024-4943 - 6.4CVE-2024-4158: Blocksy <= 2.0.42 Stored Cross-Site Scripting
CVE-2024-4158 - 6.4CVE-2024-3747: Blocksy <= 2.0.39 Stored Cross-Site Scripting
CVE-2024-3747 - 6.4CVE-2024-32961: Blocksy <= 2.0.33 Stored Cross-Site Scripting
CVE-2024-32961
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C