CVE-2022-1914: The Clean-Contact WordPress plugin through 1.6 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 lea

medium Affects clean-contact (WordPress plugin). Feed 2026.10.29.1, updated 2026-10-28; published 2022-06-27; advisory modified 2026-06-17.

The Clean-Contact WordPress plugin through 1.6 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 lea

Package: clean-contact (WordPress plugin) WordPress
Affected versions: <=1.6
Fixed in: no fix recorded
Severity: medium CVSS 4.3
Exploitation: not on CISA KEV · EPSS 0% (37.0th percentile)
Published: 2022-06-27
Source: nvd

References

CWE-352

NVD record clean-contact (WordPress plugin) advisories

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs How findings are ranked

Related advisories

CVE-2019-9787 high WordPress before 5.1.1 does not properly filter comment content, leading to Remote Code Ex same weakness: CWE-352
CVE-2016-6897 medium Cross-site request forgery (CSRF) vulnerability in the wp_ajax_update_plugin function in w same weakness: CWE-352
CVE-2022-1020 critical The Product Table for WooCommerce (wooproducttable) WordPress plugin before 3.1.2 does not same weakness: CWE-352
CVE-2019-12616 medium phpMyAdmin CSRF Vulnerability same weakness: CWE-352
CVE-2020-5776 high Cross-Site Request Forgery in MAGMI same weakness: CWE-352
CVE-2022-1574 critical The HTML2WP WordPress plugin through 1.0.0 does not have authorisation and CSRF checks whe same weakness: CWE-352