CVE-2025-64369
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.58.
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 confidenceThe Contact Form Email WordPress plugin versions up to 1.3.58 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This broken access control issue likely permits unauthorized users to access or modify contact form data or settings they should not have permission to view or change.
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.
-
Verify the Contact Form Email plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'contact-form-email' or similar. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to confirm the plugin appears in the list.Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins and locate 'Contact Form Email' in the list. The version number is displayed below the plugin name. Alternatively, open the main plugin file (usually contact-form-email.php) and look for the 'Version:' header comment.Affected if The installed version is 1.3.58 or any version lower than 1.3.58
-
Check for WordPress user roles with elevated accessNavigate to Users > All Users in the WordPress admin dashboard. Review the roles assigned to each user (Administrator, Editor, Author, Contributor, Subscriber). Pay particular attention to any users with custom roles or limited roles that should not have access to form settings.Affected if Users with roles below Administrator (such as Editors, Authors, or Contributors) have access to the plugin settings or form data pages
-
Test access to plugin admin pages with limited usersLog in with a non-administrator account (e.g., Editor or Author role). Attempt to navigate to the Contact Form Email plugin settings page or any admin pages created by this plugin. Observe whether access is granted without proper capability checks.Affected if A non-administrator user can access plugin admin pages, settings, or form data that should require Administrator privileges
A user is affected if the Contact Form Email plugin version is 1.3.58 or lower AND non-administrator users can access plugin settings or form data they should not be able to view or modify.
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 dataImplement proper authorization checks (capability verification and nonce validation) on all sensitive plugin functions and admin pages to verify user permissions before allowing access to protected resources.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64369 — 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-2025-64369 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