Skip to main content
VulnerabilityPublished

CVE-2026-126012: The Contact Form Email plugin for WordPress is vulnerable to authorization bypass in all versions up

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-126012· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 20 Nov 2026, 11:34 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–

AI-suggested

Users should restrict subscriber-level access where possible and monitor for plugin updates addressing this issue. Since the nonce protection is ineffective, relying on it for authorization is insufficient. Until a fix is released, consider disabling or replacing the plugin to prevent exploitation.

Description

The Contact Form Email plugin for WordPress up to version 1.3.72 has an authorization bypass vulnerability. This flaw allows authenticated users with subscriber-level access or higher to perform unauthorized actions such as viewing and deleting all stored contact form submissions, managing forms, altering plugin database tables, and configuring the plugin to email submission data to an attacker-controlled address. The vulnerability arises because the plugin does not properly verify user authorization and the nonce protection is ineffective against subscriber-level users.

References

Community reviews

Loading reviews…