The issue is related to the lack of CSRF checks when saving settings, which could allow attackers to make changes to the settings of a logged-in admin. Additionally, the plugin allows arbitrary HTML to be inserted in one of its settings, leading to a potential Stored XSS issue. This could be triggered in the backend, frontend, or both, depending on the payload used.