Skip to main content
VulnerabilityPublished

CVE-2026-126012: Contact Form Email (WordPress plugin) · Missing Authorization

Affects Contact Form Email (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 20 Nov 2026, 08:04 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.14.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
codepeopleContact Form EmailAffected
  • <=1.3.72
Fixed in–

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.

References

Community reviews

Loading reviews…