Skip to main content
Menu
CVEs

Contact Form Email missing authorization in form submissions

CVE-2026-126012Published November 20, 2026, updated

4.3MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Contact Form Email plugin for WordPress, from codepeople, has a missing authorization flaw that lets any logged-in user with Subscriber-level access or higher exploit it remotely over the network. Such an attacker can view and delete all stored contact form submissions, create, rename, delete, and clone forms, alter plugin database tables, and change the reporting settings so that every submission is silently emailed as a CSV to an address the attacker controls.

Written by a model

Original description

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.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126012 (Contact Form Email <= 1.3.72 - Missing Authorization to Authenticated (Subscriber+) Sensitive Data Access and Plugin Settings Modification…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126012 (entry last updated 2026-11-20):
Affected:
- codepeople Contact Form Email: through 1.3.72
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126012 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126012 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/ba761f22-d3fa-4ac8-99a0-cc260c147562?source=cve
- https://plugins.trac.wordpress.org/browser/contact-form-to-email/tags/1.3.72/cp-main-class.inc.php#L534
- https://plugins.trac.wordpress.org/browser/contact-form-to-email/tags/1.3.72/cp-main-class.inc.php#L515
- https://plugins.trac.wordpress.org/browser/contact-form-to-email/tags/1.3.72/cp-admin-int-list.inc.php#L7
- https://plugins.trac.wordpress.org/browser/contact-form-to-email/tags/1.3.72/classes/cp-base-class.inc.php#L34
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3795422%40contact-form-to-email&new=3795422%40contact-form-to-email
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126012
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126012"}.

Affected versions

cve.now Index

12Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.3/10CVSS 4.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 8

Questions about CVE-2026-126012

Is CVE-2026-126012 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-126012?

Contact Form Email: through 1.3.72.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.