HomeWordPress vulnerabilitiesGetwid
Getwid vulnerabilities
Getwid has 10 known vulnerabilities in this database. The most recent published record is dated 23 Sep 2026.
- Known vulnerabilities
- 10
- Active installs
- 50,000+
- Latest version
- 3.0.2
- Last updated
- 16 Sep 2026
- Most recent
- 23 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-5924 | Medium 6.4 | Up to 2.1.3 | Fixed in a later version (latest 3.0.2) | 23 Sep 2026 |
| Cross-site scripting (XSS) CVE-2024-10872 | Medium 6.4 | Up to 2.0.12 | Fixed in a later version (latest 3.0.2) | 20 Nov 2024 |
| Broken access control CVE-2024-6491 | Medium 4.3 | Up to 2.0.10 | Fixed in a later version (latest 3.0.2) | 20 Jul 2024 |
| Broken access control CVE-2024-6489 | Medium 5.3 | Up to 2.0.10 | Fixed in a later version (latest 3.0.2) | 20 Jul 2024 |
| Cross-site scripting (XSS) CVE-2024-3588 | Medium 6.4 | Up to 2.0.7 | Fixed in a later version (latest 3.0.2) | 2 May 2024 |
| Cross-site scripting (XSS) CVE-2024-1948 | Medium 6.4 | Before 2.0.6 | Fixed in 2.0.6 | 9 Apr 2024 |
| Broken access control CVE-2023-6959 | Medium 4.3 | Before 2.0.5 | Fixed in 2.0.5 | 5 Feb 2024 |
| Security weakness CVE-2023-6963 | Medium 5.3 | Before 2.0.5 | Fixed in 2.0.5 | 5 Feb 2024 |
| Broken access control CVE-2023-1910 | Medium 4.3 | Up to 1.8.3 | Fixed in a later version (latest 3.0.2) | 9 Jun 2023 |
| Server-side request forgery (SSRF) CVE-2023-1895 | High 8.5 | Up to 1.8.3 | Fixed in a later version (latest 3.0.2) | 9 Jun 2023 |
Read the published descriptions
- CVE-2026-5924, 23 Sep 2026
- The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Google Maps block's 'customStyle' attribute in all versions up to, and including, 2.1.3. This is due to the use of eval() on user-controlled block content in the frontend JavaScript mapStyles() function. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-10872, 20 Nov 2024
- The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `template-post-custom-field` block in all versions up to, and including, 2.0.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-6491, 20 Jul 2024
- The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the mailchimp_api_key_manage 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. CVE record
- CVE-2024-6489, 20 Jul 2024
- 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. CVE record
- CVE-2024-3588, 2 May 2024
- The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Countdown block in all versions up to, and including, 2.0.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-1948, 9 Apr 2024
- The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the block content in all versions up to, and including, 2.0.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-6959, 5 Feb 2024
- The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the recaptcha_api_key_manage function in all versions up to, and including, 2.0.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to add, modify, or delete the 'Recaptcha Site Key' and 'Recaptcha Secret Key' settings. CVE record
- CVE-2023-6963, 5 Feb 2024
- The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to CAPTCHA Bypass in versions up to, and including, 2.0.4. This makes it possible for unauthenticated attackers to bypass the Captcha Verification of the Contact Form block by omitting 'g-recaptcha-response' from the 'data' array. CVE record
- CVE-2023-1910, 9 Jun 2023
- The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to unauthorized modification of data due to an insufficient capability check on the get_remote_templates function in versions up to, and including, 1.8.3. This makes it possible for authenticated attackers with subscriber-level permissions or above to flush the remote template cache. Cached template information can also be accessed via this endpoint but these are not considered sensitive as they are publicly accessible from the developer's site. CVE record
- CVE-2023-1895, 9 Jun 2023
- The Getwid - Gutenberg Blocks plugin for WordPress is vulnerable to Server Side Request Forgery via the get_remote_content REST API endpoint in versions up to, and including, 1.8.3. This can allow authenticated attackers with subscriber-level permissions or above to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. CVE record
What to do if you run Getwid
If you run Getwid, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Getwid vulnerabilities
Free. We email you when a new vulnerability is published for Getwid, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.