Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-6489: CWE-862 Missing Authorization in jetmonsters Getwid – Gutenberg Blocks

0
Medium
VulnerabilityCVE-2024-6489cvecve-2024-6489cwe-862
Published: Sat Jul 20 2024 (07/20/2024, 06:43:48 UTC)
Source: CVE Database V5
Vendor/Project: jetmonsters
Product: Getwid – Gutenberg Blocks

Description

CVE-2024-6489 is a medium severity vulnerability in the Getwid – Gutenberg Blocks WordPress plugin that allows authenticated users with Contributor-level access or higher to modify the MailChimp API key due to missing authorization checks. The flaw exists in the get_google_api_key function, which lacks proper capability verification, enabling unauthorized data modification. Exploitation requires no user interaction beyond having Contributor or higher privileges. While it does not impact confidentiality or availability, it compromises integrity by allowing unauthorized changes to API keys, potentially leading to further misuse. No known exploits are currently reported in the wild. Organizations using this plugin should apply patches or implement strict access controls to mitigate risk. Countries with significant WordPress usage and active Getwid plugin deployments, such as the United States, Germany, United Kingdom, Canada, Australia, and India, are most likely affected.

AI-Powered Analysis

AILast updated: 02/26/2026, 03:12:09 UTC

Technical Analysis

CVE-2024-6489 identifies a missing authorization vulnerability (CWE-862) in the Getwid – Gutenberg Blocks plugin for WordPress, specifically affecting all versions up to and including 2.0.10. The vulnerability arises from the get_google_api_key function, which lacks a proper capability check, allowing authenticated users with Contributor-level permissions or higher to modify the MailChimp API key stored by the plugin. This missing authorization means that users who normally should not have permission to alter API keys can do so, potentially leading to unauthorized changes in the plugin's integration with MailChimp services. The vulnerability does not require elevated privileges beyond Contributor, nor does it require user interaction, making it relatively easy to exploit within environments where such user roles exist. The CVSS v3.1 score is 5.3 (medium), reflecting that the attack vector is network-based, with low attack complexity, no privileges required beyond Contributor, no user interaction, and limited impact on integrity only. There is no impact on confidentiality or availability. No patches were linked at the time of publication, and no known exploits in the wild have been reported. The vulnerability could be leveraged to alter API keys, potentially enabling unauthorized access or manipulation of MailChimp integrations, which could affect marketing campaigns or data flows reliant on these keys.

Potential Impact

The primary impact of CVE-2024-6489 is unauthorized modification of the MailChimp API key within the affected WordPress plugin. This compromises the integrity of the plugin's configuration and could lead to misuse of MailChimp services, such as unauthorized email campaigns, data exfiltration, or disruption of marketing workflows. While the vulnerability does not directly expose sensitive data or cause denial of service, the ability to alter API keys can indirectly lead to reputational damage, loss of customer trust, and potential compliance issues if unauthorized communications occur. Organizations with Contributor-level users or higher on WordPress sites using this plugin are at risk. Attackers could exploit this vulnerability to escalate their influence within the marketing infrastructure or pivot to other attacks leveraging compromised API credentials. The scope is limited to environments where the plugin is installed and Contributor or higher roles exist, but given WordPress's widespread use, the potential impact is significant for affected sites.

Mitigation Recommendations

To mitigate CVE-2024-6489, organizations should immediately update the Getwid – Gutenberg Blocks plugin to a patched version once available. In the absence of an official patch, administrators should restrict Contributor-level permissions and above to trusted users only, minimizing the risk of exploitation. Implementing strict role-based access controls and auditing user roles regularly can reduce exposure. Additionally, monitoring and rotating MailChimp API keys periodically will limit the window of opportunity for misuse. Site administrators can also consider temporarily disabling the plugin or removing Contributor-level user capabilities until a fix is applied. Reviewing and hardening WordPress security configurations, including limiting plugin installations and enforcing the principle of least privilege, will further reduce risk. Finally, monitoring logs for unusual changes to API keys or plugin settings can help detect exploitation attempts early.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-07-03T18:48:41.173Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6c04b7ef31ef0b55f002

Added to database: 2/25/2026, 9:39:16 PM

Last enriched: 2/26/2026, 3:12:09 AM

Last updated: 2/26/2026, 12:44:19 PM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats