dbcve.org
Cp Contact Form With PaypalWordPress extension · Codepeople

CVE-2023-27460

HIGH · 8.8 CVSS v3.1 Published 2024-06-03
Fix available
A fix is available. Upgrade to 1.3.35 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Missing Authorization vulnerability in CodePeople, paypaldev CP Contact Form with Paypal allows Functionality Misuse.This issue affects CP Contact Form with Paypal: from n/a through 1.3.34.

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 confidence

A Missing Authorization vulnerability in the CP Contact Form with Wordpress plugin allows attackers to misuse certain functionality due to inadequate permission checks. This could permit unauthenticated or low-privilege users to access administrative or privileged operations that should require proper authorization.

MitigationImplement proper authorization checks (e.g., WordPress capability checks like current_user_can()) on all sensitive functions and AJAX endpoints in the plugin. Update to version 1.3.35 or later if available, or disable the plugin until a patched version is released.

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
Cp Contact Form With PaypalWordPress extension
Affected:< 1.3.35

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
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Codepeople Cp Contact Form With Wordpress' or 'CP Contact Form with Wordpress' in the list of active plugins.
    Affected if The plugin appears in the list of installed plugins (either active or inactive).
  2. Identify the installed version
    In the WordPress admin under Plugins > Installed Plugins, find the plugin entry. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (usually cp-contact-form-with-paypal.php) and check the 'Version' field in the plugin header comment.
    Affected if The version number displayed is less than 1.3.35.
  3. Confirm the exact version for comparison
    If the version is not clearly displayed in the admin, access the site via FTP or file manager and locate the plugin directory (wp-content/plugins/cp-contact-form-with-paypal/). Open the main plugin PHP file and read the Version: X.X.X value from the file header.
    Affected if The version read from the file header is 1.3.34, 1.3.33, or any version lower than 1.3.35.

You are affected if the Codepeople Cp Contact Form With Wordpress plugin is installed and its version is lower than 1.3.35.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.3.35 or later
Fixed in 1.3.35
Interim mitigation

Implement proper authorization checks (e.g., WordPress capability checks like current_user_can()) on all sensitive functions and AJAX endpoints in the plugin. Update to version 1.3.35 or later if available, or disable the plugin until a patched version is released.

Recommended fix High confidence

CP Contact Form with Paypal version 1.3.35

  1. Backup your WordPress site before making any changes
  2. Navigate to the WordPress admin dashboard > Plugins section
  3. Locate 'CP Contact Form with Paypal' in the installed plugins list
  4. Click 'Update now' on the plugin if an update is available, or manually upload version 1.3.35
  5. After updating, verify the plugin is running version 1.3.35 or later in the Plugins list
  6. Test the contact form functionality to ensure it works correctly post-update
  7. Confirm that authorization controls are functioning properly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cp Contact Form With Paypal Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-27460 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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