CVE-2023-27460 is a missing authorization flaw in the CP Contact Form with PayPal plugin for WordPress. NVD scores it 4.3, Medium. Versions up to 1.3.34 are affected, and Patchstack lists 1.3.35 as the fix. It lets a low-privileged user misuse feedback submission.
What's affected
- CP Contact Form with PayPal 1.3.34 and earlier: affected.
- Version 1.3.35: the fixed release, per Patchstack.
Patchstack says the attacker needs the Subscriber role and rates the priority Low. The record describes the effect as functionality misuse, and the Patchstack title says feedback submission. NVD scores 4.3 and Patchstack gives the same figure, so there is no conflict on severity.
How to check if you're exposed
With WP-CLI:
wp plugin list --name=cp-contact-form-with-paypal --fields=name,status,version,update
Or read the version on the Plugins page of the WordPress dashboard. If it shows 1.3.34 or lower, update. If the plugin is installed but not used, remove it, because an unused plugin still adds code to the site.
What to do now
- Update the plugin to 1.3.35 or later.
- If you no longer use the plugin, deactivate and delete it.
- Check whether Subscriber registration is open on the site and whether you need it to be.
- Review feedback submissions for entries you did not expect.
- Check the Gold page for this CVE for later revisions.
Why it matters
The weakness class is CWE-862 (Missing Authorization). A function that should check whether the current user is allowed to perform an action does not check. The request may be accepted from any account that can reach it.
This one is low impact on its own. It matters for two reasons. First, small authorization gaps show where a plugin's checks are thin. Second, the cost of fixing it is a single update. A Medium score with a one-step fix is an easy item to clear from a backlog.
Authorization bugs in WordPress plugins often come from one pattern. A function is registered so that logged-in users can call it, and the developer checks that the user is logged in but not what the user is allowed to do. The usual fix is a capability check, so the function only runs for users who hold the right role.
For site owners the useful question is who holds an account. Many sites keep old Subscriber accounts from sign-ups, newsletters or past customers. Clearing out stale accounts reduces the number of people who can reach low-privilege bugs of every kind.
Quick check
Is a 4.3 score worth acting on?
Yes if the plugin is active, since the fix is a version bump. The limited effect is why the priority is Low, not a reason to leave it unpatched.
Sources
Last reviewed: 19 October 2026.