HomeWordPress vulnerabilitiesContact Form Email
Contact Form Email vulnerabilities
Contact Form Email has 8 known vulnerabilities in this database. The most recent published record is dated 20 Nov 2026.
- Known vulnerabilities
- 8
- Active installs
- 8,000+
- Latest version
- 1.3.74
- Last updated
- 11 Nov 2026
- Most recent
- 20 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-126012 | Medium 4.3 | Up to 1.3.72 | Fixed in a later version (latest 1.3.74) | 2 d ago |
| Cross-site scripting (XSS) CVE-2026-112379 | High 7.1 | Up to 1.3.68 | Fixed in a later version (latest 1.3.74) | 22 Oct 2026 |
| Cross-site scripting (XSS) CVE-2023-5955 | Medium 4.8 | Before 1.3.44 | Fixed in 1.3.44 | 11 Dec 2023 |
| Cross-site scripting (XSS) CVE-2023-2718 | Medium 5.4 | Before 1.3.38 | Fixed in 1.3.38 | 12 Jun 2023 |
| Cross-site scripting (XSS) CVE-2021-42361 | Medium 4.8 | Up to 1.3.24 | Fixed in a later version (latest 1.3.74) | 17 Nov 2021 |
| Cross-site scripting (XSS) CVE-2018-20963 | Medium 6.1 | Before 1.2.66 | Fixed in 1.2.66 | 13 Aug 2019 |
| Cross-site request forgery (CSRF) CVE-2018-20964 | High 8.8 | Before 1.2.66 | Fixed in 1.2.66 | 13 Aug 2019 |
| Cross-site scripting (XSS) CVE-2019-9646 | Medium 6.1 | Before 1.2.66 | Fixed in 1.2.66 | 10 Mar 2019 |
Read the published descriptions
- CVE-2026-126012, 20 Nov 2026
- The Contact Form Email plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.3.72. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to view and delete all stored contact form submissions, create, rename, delete, and clone forms, alter plugin database tables, and persistently rewrite the reporting options to silently email a CSV of all submissions to an attacker-controlled address on every subsequent request. The nonce intended to authorize state-changing POST requests is minted into the same management page the attacker can already render, so it provides no effective authorization barrier against a Subscriber-level user. CVE record
- CVE-2026-112379, 22 Oct 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Codepeople Contact Form Email contact-form-to-email allows Stored XSS.This issue affects Contact Form Email: from n/a through 1.3.68. CVE record
- CVE-2023-5955, 11 Dec 2023
- The Contact Form Email WordPress plugin before 1.3.44 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2023-2718, 12 Jun 2023
- The Contact Form Email WordPress plugin before 1.3.38 does not escape submitted values before displaying them in the HTML, leading to a Stored XSS vulnerability. CVE record
- CVE-2021-42361, 17 Nov 2021
- The Contact Form Email WordPress plugin is vulnerable to Stored Cross-Site Scripting due to insufficient input validation and escaping via the name parameter found in the ~/trunk/cp-admin-int-list.inc.php file which allowed attackers with administrative user access to inject arbitrary web scripts, in versions up to and including 1.3.24. This affects multi-site installations where unfiltered_html is disabled for administrators, and sites where unfiltered_html is disabled. CVE record
- CVE-2018-20963, 13 Aug 2019
- The contact-form-to-email plugin before 1.2.66 for WordPress has XSS. CVE record
- CVE-2018-20964, 13 Aug 2019
- The contact-form-to-email plugin before 1.2.66 for WordPress has CSRF. CVE record
- CVE-2019-9646, 10 Mar 2019
- The Contact Form Email plugin before 1.2.66 for WordPress allows wp-admin/admin.php item XSS, related to cp_admin_int_edition.inc.php in the "custom edition area." CVE record
What to do if you run Contact Form Email
If you run Contact Form Email, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Contact Form Email vulnerabilities
Free. We email you when a new vulnerability is published for Contact Form Email, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.