Vayu Blocks – Gutenberg Blocks for WordPress & WooCommerce <= 1.1.1 - Missing Authorization to Unauthenticated Arbitrary Plugin Installation/Activation
Strategic Overview
- Status
- Patched in 1.2.0
- Affected Plugin
- Vayu Blocks – Website Builder for the Gutenberg Block Editor
- Affected Version
<= 1.1.1- CVSS
- 9.8Critical
- Weakness type
- CWE-284 · Improper Access Control
- CVE
CVE-2024-10124
At a glance
CVE-2024-10124 is a critical-severity Improper Access Control vulnerability in the Vayu Blocks WordPress plugin, affecting versions <= 1.1.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.2.0; sites on affected versions should update now. Disclosed December 2024, reported by stealthcopter.
Vulnerability Overview
The Vayu Blocks – Gutenberg Blocks for WordPress & WooCommerce plugin for WordPress is vulnerable to unauthorized arbitrary plugin installation and activation due to a missing capability check on the tp_install() function in all versions up to, and including, 1.1.1. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins which can be leveraged to achieve remote code execution if another vulnerable plugin is installed and activated. This vulnerability was partially patched in version 1.1.1.
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, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-284: Improper Access Control
Vayu Blocks <= 1.1.1 carries this weakness at tp_install(), and reaching it takes no account at all. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.
Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For Vayu Blocks the fix is 1.2.0: builds <= 1.1.1 are affected, anything from 1.2.0 onward is not.
Remediation
Update to version 1.2.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Vayu Blocks 1.2.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Vayu Blocks – Website Builder for the Gutenberg Block Editor
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C