CVE-2025-47465

Blocksy <= 2.0.97 - Missing Authorization

2025-05-07 00:00
SavPhill (Savphill)

Strategic Overview

Status
Patched in 2.0.98
Affected Theme
Blocksy
Affected Version
<= 2.0.97
CVSS
2.7Low
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-47465
View all Blocksy vulnerabilities

At a glance

CVE-2025-47465 is a low-severity Missing Authorization vulnerability in the Blocksy WordPress theme, affecting versions <= 2.0.97. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.0.98; sites on affected versions should update now. Disclosed May 2025, reported by SavPhill (Savphill).

Vulnerability Overview

The Blocksy theme for WordPress is vulnerable to unauthorized access due to a missing capability check on the wp_ajax_blocksy_notice_button_click AJAX endpoint in versions up to, and including, 2.0.97. This makes it possible for authenticated attackers, with administrator-level access and above, to install plugins. This would only impact sites where administrators have been stripped of their capability to install and activate plugins, which might occur on multi-sites.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Blocksy <= 2.0.97 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Blocksy the fix is 2.0.98: builds <= 2.0.97 are affected, anything from 2.0.98 onward is not.

Remediation

Update to version 2.0.98, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Blocksy 2.0.98 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C