Live › vulnerability › CVE-2026-116761
Go to dashboardThe CMB2 plugin for WordPress up to and including 2.13.4 fails to sanitize and escape a wysiwyg field inside a repeatable group submitted through its front-end form helper. An unauthenticated visitor can store a script that runs in the browser of anyone who opens the affected page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 07:31 UTC. All times on this page are UTC.
Only sites that run CMB2 up to 2.13.4 and render its front-end form helper with a wysiwyg field inside a repeatable group on a publicly accessible page are exposed. Sites that use CMB2 only in the admin area or do not expose that front-end form can skip it.
No product ranges from the sources yet.
cmb2/init.php; versions 2.13.4 and below are in scope.wysiwyg field inside a repeatable group on public pages.2.13.4; the sources do not name the exact fixed version.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The CMB2 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'cmb43ex1_grp[0][txt] (wysiwyg field inside group — field id controlled by integrator config)' parameter in all versions up to, and including, 2.13.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable when a site integrator renders the plugin's documented front-end form helper with a wysiwyg field inside a repeatable group on a publicly accessible page.
This page as .md · .json · in your agent: get_signal("CVE-2026-116761")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.