CVE-2025-10019
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 · uneditedAuthorization Bypass Through User-Controlled Key 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.60.
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 up to version 1.3.60 contains an authorization bypass vulnerability where the access control logic relies on a user-controllable key parameter. An attacker can manipulate this key to bypass authentication checks and access unauthorized form data or administrative functions.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Locate the Contact Form Email pluginCheck the wp-content/plugins/ directory for a folder named 'contact-form-email' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'Contact Form Email' in the list.Affected if The plugin is found installed on the WordPress site
-
Identify the installed versionIn WordPress admin, click on the plugin from the Installed Plugins list to view its details, which displays the version number. Alternatively, open the main plugin PHP file (usually contact-form-email.php) and look for the 'Version' header in the plugin comment block.Affected if The version displayed is 1.3.60 or any earlier version up to and including 1.3.60
-
Compare version against the affected rangeCompare your identified version to the affected range: any version from 1.0 through 1.3.60 is vulnerable. Version 1.3.61 and later are patched.Affected if The installed version is 1.3.60 or earlier, meaning the plugin relies on user-controllable key parameters for access control decisions
-
Verify the vulnerability exists in the code (optional deeper check)Examine the plugin code for endpoints or functions that perform access control checks using a key parameter passed from user input (such as $_GET, $_POST, or $_REQUEST). Look for logic that grants access based solely on a key value without validating user session or permissions.Affected if The code contains access control logic that grants authorization based purely on a user-supplied key parameter rather than authenticated user sessions
If the Contact Form Email plugin is installed and the version is 1.3.60 or earlier, the environment is affected by this authorization bypass 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 which implements proper server-side authorization validation that does not rely on user-controllable parameters for access control decisions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10019 — 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-10019 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