Plugins · getwid · data as of 2026-11-04
Is Getwid safe? Known vulnerabilities and latest version
- Latest version
- 3.0.2
- Last updated
- 2026-09-16
- Active installs
- 50,000+
- Known issues on record
- 13
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
40+ Gutenberg Blocks, plus multiple pre-made free block templates for the WordPress block editor. — by jetmonsters
What to do
- Update to the latest version (3.0.2). Anything older than 3.0.2 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get getwid --field=version shows what you run; wp plugin update getwid updates it.
Check your version
Known vulnerabilities
13 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.4 CVE-2026-91862 · published 2026-10-10
Stored cross-site scripting (XSS) in Getwid (3.0.1 and older)
- Affected
- 3.0.1 and older
- Fixed in
- 3.0.2 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Getwid – Gutenberg Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data-image-points' parameter in all versions up to, and including, 3.0.1 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.
medium 6.4 CVE-2026-5924 · published 2026-09-23
Stored cross-site scripting (XSS) in Getwid (2.1.3 only)
- Affected
- 2.1.3 only
- Fixed in
- 2.2.0 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-5924Wordfence advisoryCode change (fix)Plugin source
medium 4.3 CVE-2025-58252 · published 2025-09-22
Information disclosure in Getwid (2.1.2 and older)
- Affected
- 2.1.2 and older
- Fixed in
- 2.1.3
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Insertion of Sensitive Information Into Sent Data vulnerability in jetmonsters Getwid getwid allows Retrieve Embedded Sensitive Data.This issue affects Getwid: from n/a through <= 2.1.2.
medium 5.4 CVE-2024-10872 · published 2024-11-20
Stored cross-site scripting (XSS) in Getwid (2.0.12 and older)
- Affected
- 2.0.12 and older
- Fixed in
- 2.0.13 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
NVD CVE-2024-10872Wordfence advisoryCode change (fix)Plugin source
medium 4.3 CVE-2024-6491 · published 2024-07-20
Missing authorization check in Getwid (2.0.10 and older)
- Affected
- 2.0.10 and older
- Fixed in
- 2.0.11 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2024-6491Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2024-6489 · published 2024-07-20
Missing authorization check in Getwid (2.0.10 and older)
- Affected
- 2.0.10 and older
- Fixed in
- 2.0.11 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
medium 5.4 CVE-2024-3588 · published 2024-05-02
Stored cross-site scripting (XSS) in Getwid (2.0.7 and older)
- Affected
- 2.0.7 and older
- Fixed in
- 2.0.8 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
NVD CVE-2024-3588Wordfence advisoryCode change (fix)github.comPlugin source
medium 5.4 CVE-2024-1948 · published 2024-04-09
Stored cross-site scripting (XSS) in Getwid (2.0.5 and older)
- Affected
- 2.0.5 and older
- Fixed in
- 2.0.6 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
medium 4.3 CVE-2023-6959 · published 2024-02-05
Missing authorization check in Getwid (2.0.4 and older)
- Affected
- 2.0.4 and older
- Fixed in
- 2.0.5 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
medium 5.3 CVE-2023-6963 · published 2024-02-05
Missing authorization check in Getwid (2.0.4 and older)
- Affected
- 2.0.4 and older
- Fixed in
- 2.0.5 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
high 7.5 CVE-2023-6042 · published 2024-01-08
Security issue in Getwid (older than 2.0.3)
- Affected
- older than 2.0.3
- Fixed in
- 2.0.3
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Any unauthenticated user may send e-mail from the site with any title or content to the admin
medium 4.3 CVE-2023-1910 · published 2023-06-09
Missing authorization check in Getwid (1.8.3 and older)
- Affected
- 1.8.3 and older
- Fixed in
- 1.8.7 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
NVD CVE-2023-1910Wordfence advisoryWordfence advisoryPlugin source
critical 9.6 CVE-2023-1895 · published 2023-06-09
Server-side request forgery (SSRF) in Getwid (1.8.3 and older)
- Affected
- 1.8.3 and older
- Fixed in
- 1.8.7 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
NVD CVE-2023-1895Wordfence advisoryWordfence advisoryPlugin source
Recent activity
- 2026-09-16 — latest release on wordpress.org (3.0.2).
- 2026-10-10 — Stored cross-site scripting (XSS) disclosed (CVE-2026-91862), fixed in 3.0.2.
- 2026-09-23 — Stored cross-site scripting (XSS) disclosed (CVE-2026-5924), fixed in 2.2.0.
- 2025-09-22 — Information disclosure disclosed (CVE-2025-58252), fixed in 2.1.3.
Get an email when Getwid has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Getwid (getwid) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by jetmonsters (8 tracked)
Types found in this plugin: Cross-site scripting (XSS) (5) · Missing authorization (5) · Sensitive data exposure (1) · Server-side request forgery (SSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/getwid (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/getwid"><img src="https://laskyr.com/plugins/getwid/badge.svg" alt="Getwid vulnerability status"></a>