CVE-2026-32483
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 · uneditedMissing 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.
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 · moderate confidenceThis is a Missing Authorization vulnerability in the codepeople Contact Form Email WordPress plugin (versions up to 1.3.63). The plugin fails to properly enforce access control checks, allowing users with insufficient privileges (likely subscribers or contributors) to access or modify settings and functionality that should be restricted to administrators. This is a classic privilege escalation/IDOR vulnerability where incorrectly configured security levels permit unauthorized actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check if Contact Form Email plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Contact Form Email' or 'codepeople Contact Form Email' in the listAffected if Plugin is not found in the installed plugins list
-
Identify installed plugin versionIn the Plugins list, find the Contact Form Email plugin and note the version number displayed below the plugin nameAffected if Version is 1.3.63 or earlier (versions 1.3.64 and later contain the fix)
-
Verify plugin is activeIn Plugins > Installed Plugins, confirm the Contact Form Email plugin shows as 'Active'Affected if Plugin is active and version is 1.3.63 or earlier
-
Review user roles with access to plugin settingsGo to Users > All Users and identify any users assigned to roles like Subscriber or Contributor who may have access to plugin functions they should notAffected if Any non-administrator users exist and the vulnerable plugin version is in use
If the Contact Form Email plugin is active at version 1.3.63 or earlier, the environment is likely affected by this missing authorization vulnerability.
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 dataUpdate the Contact Form Email plugin to the latest version (1.3.64 or later) which should contain proper authorization fixes. If no update is available, review all admin-facing functions and add proper capability checks (e.g., current_user_can('manage_options')) before executing sensitive operations.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32483 — 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-2026-32483 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