The CMB2 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'file_list' Field…

Why it is Yellow

• CVSS 7.2 high
• Remotely exploitable without logging in

References

• https://plugins.trac.wordpress.org/browser/cmb2/tags/2.13.0/includes/CMB2_Field.php#L617
• https://plugins.trac.wordpress.org/browser/cmb2/tags/2.13.0/includes/CMB2_Field.php#L748
• https://plugins.trac.wordpress.org/browser/cmb2/tags/2.13.0/includes/CMB2_Hookup.php#L953
• https://plugins.trac.wordpress.org/browser/cmb2/tags/2.13.0/includes/CMB2_Sanitize.php#L100
• https://plugins.trac.wordpress.org/browser/cmb2/tags/2.13.0/includes/CMB2_Utils.php#L690
• https://plugins.trac.wordpress.org/browser/cmb2/tags/2.13.0/includes/helper-functions.php#L320
• https://plugins.trac.wordpress.org/browser/cmb2/tags/2.13.0/includes/types/CMB2_Type_File_List.php#L51
• https://plugins.trac.wordpress.org/changeset?reponame=&old=3712103%40cmb2&new=3712103%40cmb2
• https://www.wordfence.com/threat-intel/vulnerabilities/id/2d61a1f1-137e-4856-b5ff-b100143a8b47?source=cve

Original description

The CMB2 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'file_list' Field Type in all versions up to, and including, 2.13.0 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 an integrating plugin or theme registers a file_list field on a publicly accessible front-end form or a user meta box, as CMB2 is a developer library and does not expose these fields by default.