Contact Form EmailWordPress extension · Codepeople
CVE-2023-48318
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 · uneditedImproper Restriction of Excessive Authentication Attempts vulnerability in CodePeople Contact Form Email allows Functionality Bypass.This issue affects Contact Form Email: from n/a through 1.3.41.
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 CodePeople Contact Form Email plugin versions through 1.3.41 contains an improper restriction of excessive authentication attempts vulnerability. Attackers can bypass rate limiting or other authentication controls on the contact form, enabling automated abuse, spam submissions, or potential brute-force attacks against the form functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Contact Form EmailWordPress extension
< 1.3.42CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Locate the CodePeople Contact Form Email pluginNavigate to your WordPress plugins directory or access the Plugins section in the WordPress admin dashboard to find the CodePeople Contact Form Email pluginAffected if The plugin is present in the installation
-
Identify the installed version numberIn the WordPress admin, view the plugin details or check the plugin header in the main PHP file (typically in wp-content/plugins/contact-form-email/ or similar) for the Version fieldAffected if A version number is displayed
-
Compare against affected version rangeCompare your installed version to the known affected range: versions through 1.3.41 are vulnerable; version 1.3.42 and later are patchedAffected if The installed version is 1.3.41 or earlier (less than 1.3.42)
If the CodePeople Contact Form Email plugin is installed and the version is 1.3.41 or earlier, the environment is affected by this rate limiting 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.
dbcve · scoped1.3.42
Update the plugin to version 1.3.42 or later to obtain the security patch. Alternatively, implement rate limiting via WAF or application-level controls as a temporary mitigation until the update can be applied.
1.3.42
- Backup your WordPress site database and files before making any changes
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Locate 'Contact Form Email' plugin in the list
- Click 'Update now' if an update is available, or manually upload version 1.3.42
- Verify the plugin updated successfully by checking the version number in the plugins list
- Test form submissions to ensure the contact form functionality works correctly after update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Contact Form Email
Scoped from the published advisory
- 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-2023-48318 — 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-2023-48318 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