CVE-2026-5924 json
Getwid <= 2.1.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via Google Maps 'customStyle'
published 2026-09-23 47 d ago modified 2026-09-23 46 d ago also EUVD-2026-85111
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 46 d ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- jetmonsters Getwid – Gutenberg Blocks
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/a0db9693-df56-44d3-9167-c21e868c3f88?source=cve
- plugins.trac.wordpress.org /browser/getwid/trunk/assets/blocks/map/frontend.js#L4
- plugins.trac.wordpress.org /browser/getwid/tags/2.1.3/assets/blocks/map/frontend.js#L4
- plugins.trac.wordpress.org /browser/getwid/trunk/includes/blocks/google-map.php#L139
- plugins.trac.wordpress.org /browser/getwid/tags/2.1.3/includes/blocks/google-map.php#L139
- plugins.trac.wordpress.org /changeset?reponame=&old=3514403%40getwid&new=3514403%40getwid
Sources
- CVE List CVE-2026-5924
- NVD CVE-2026-5924
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.