Getwid – Gutenberg Blocks <= 2.0.10 - Missing Authorization to Google API key update
Strategic Overview
- Status
- Patched in 2.0.11
- Affected Plugin
- Getwid – Gutenberg Blocks
- Affected Version
<= 2.0.10- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-6489
At a glance
CVE-2024-6489 is a medium-severity Missing Authorization vulnerability in the Getwid WordPress plugin, affecting versions <= 2.0.10. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.11; sites on affected versions should update now. Disclosed July 2024, reported by Peter Thaleikis.
Vulnerability Overview
The Getwid – Gutenberg Blocks plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the get_google_api_key function in all versions up to, and including, 2.0.10. This makes it possible for authenticated attackers, with Contributor-level access and above, to set the MailChimp API key.
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.
CWE-862: Missing Authorization
Reaching this weakness in Getwid <= 2.0.10 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 Getwid the fix is 2.0.11: builds <= 2.0.10 are affected, anything from 2.0.11 onward is not.
Remediation
Update to version 2.0.11, 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: Getwid 2.0.11 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Getwid – Gutenberg Blocks
- 8.5CVE-2023-1895: Getwid – Gutenberg Blocks <= 1.8.3 SSRF
CVE-2023-1895 - 6.4CVE-2024-5020: Multiple Plugins <= Stored DOM-Based XSS
CVE-2024-5020 - 6.4CVE-2024-10872: Getwid – Gutenberg Blocks <= 2.0.12 Stored XSS
CVE-2024-10872 - 6.4CVE-2024-3588: Getwid – Gutenberg Blocks <= 2.0.7 DOM-Based Stored XSS
CVE-2024-3588 - 6.4CVE-2024-1948: Getwid – Gutenberg Blocks <= 2.0.5 Stored XSS
CVE-2024-1948 - 5.3CVE-2023-6963: Getwid – Gutenberg Blocks <= 2.0.4 Captcha Bypass
CVE-2023-6963 - 5.3CVE-2023-6042: Getwid – Gutenberg Blocks Improper Input Validation
CVE-2023-6042 - 4.3CVE-2025-58252: Getwid <= 2.1.2 Sensitive Information Exposure
CVE-2025-58252
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C