LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32483: WordPress Contact Form Email plugin <= 1.3.63 - Broken Access Control vulnerability

Missing Authorization vulnerability in codepeople Contact Form Email contact-form-to-email allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Contact Form Email: from n/a through <= 1.3.63.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32483 is a broken access control issue in the WordPress Contact Form Email plugin by codepeople, affecting versions up to 1.3.63. A logged-in user could access data they should not be authorized to see. The primary business concern is unauthorized exposure of form-submitted information.

Executive priority

Treat as a moderate-priority confidentiality issue. Prioritize sites collecting sensitive contact form submissions or allowing user registration. Action should focus on identifying affected WordPress installations and applying vendor-confirmed remediation when available.

Technical view

The CVE describes CWE-862 missing authorization in the contact-form-to-email WordPress plugin. CVSS 3.1 is 6.5, with network access, low privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact documented.

Likely exposure

Exposure is limited to WordPress sites running Contact Form Email/contact-form-to-email versions through 1.3.63. The CVSS vector requires a low-privileged authenticated user, so public anonymous exploitation is not indicated by the provided sources.

Exploitation context

The sources do not report active exploitation, and the CVE is not marked as KEV. The likely abuse scenario is a low-privileged WordPress account accessing plugin-related data without proper authorization. No public exploit details are included in the provided bundle.

Researcher notes

The public record provides limited technical detail beyond missing authorization and affected versions through 1.3.63. No fixed version, exploit availability, or vulnerable function is identified in the supplied sources. Avoid assuming endpoint names or exploit mechanics without vendor details.

Mitigation direction

  • Inventory WordPress sites for the Contact Form Email plugin.
  • Identify installations running contact-form-to-email version 1.3.63 or earlier.
  • Check the vendor, WordPress plugin page, or Patchstack for a fixed version or guidance.
  • Restrict unnecessary low-privileged WordPress accounts until remediation is confirmed.
  • Back up the site before plugin changes or removal.

Validation and detection

  • Confirm plugin name, slug, and installed version on each WordPress site.
  • Review WordPress user accounts with subscriber or other low-privilege roles.
  • Check site logs for unusual authenticated access to plugin-related areas.
  • Verify remediation against vendor or Patchstack guidance when available.
  • Document affected sites and remediation status for follow-up.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32483 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-32483Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
codepeopleContact Form Emailcontact-form-to-email, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.