Contact Form EmailWordPress extension · Codepeople
CVE-2018-20964
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe contact-form-to-email plugin before 1.2.66 for WordPress has CSRF.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe contact-form-to-email WordPress plugin before version 1.2.66 is vulnerable to Cross-Site Request Forgery (CSRF). This allows attackers to trick authenticated administrators into performing unintended actions, such as modifying plugin settings or form configurations, by leveraging the lack of proper CSRF token validation in plugin functions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Contact Form EmailWordPress extension
< 1.2.66CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Contact Form to Email plugin filesCheck your WordPress wp-content/plugins directory for a folder named 'contact-form-to-email' or 'codepeople-contact-form-email'. If using a file manager or SSH, list the contents of /wp-content/plugins/ and look for these folder names.Affected if The plugin folder does not exist, meaning the plugin is not installed.
-
Read the installed plugin versionOpen the main plugin PHP file (usually the first PHP file in the plugin folder) and look for the 'Version:' header comment in the file's metadata, or check the readme.txt file for the 'Stable tag:' entry.Affected if The version number shown is lower than 1.2.66 (for example, 1.2.65, 1.2.60, or any version below 1.2.66).
-
Verify plugin status in WordPress adminLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate the Contact Form to Email plugin entry and check its status (Active or Inactive).Affected if The plugin is active. An inactive plugin would require an attacker to first trick an admin into activating it before exploiting CSRF.
-
Confirm the vulnerability applies to your configurationSince this is a CSRF vulnerability requiring an authenticated administrator session, verify that your WordPress site allows administrator accounts. CSRF attacks rely on tricking logged-in admins into clicking malicious links.Affected if Administrator accounts exist on your WordPress site and the plugin is active and vulnerable (version < 1.2.66).
You are affected if the Contact Form to Email plugin is installed, active, and running a version lower than 1.2.66 on your WordPress site.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.2.66
Update the contact-form-to-email plugin to version 1.2.66 or later to patch the CSRF vulnerability. If immediate updates are not possible, disable the plugin until a patch can be applied.
Fix this in Contact Form Email
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-20964 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data