Cp Contact Form With PaypalWordPress extension · Codepeople
CVE-2015-9233
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 · uneditedThe cp-contact-form-with-paypal (aka CP Contact Form with PayPal) plugin before 1.1.6 for WordPress has CSRF with resultant XSS, related to cp_contactformpp.php and cp_contactformpp_admin_int_list.inc.php.
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 · high confidenceThe CP Contact Form with PayPal plugin before version 1.1.6 contains a CSRF vulnerability in cp_contactformpp.php and cp_contactformpp_admin_int_list.inc.php that allows attackers to forge requests that result in stored XSS, likely due to missing anti-CSRF tokens and inadequate input validation on form submissions.
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
< 1.1.6CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the CP Contact Form with PayPal plugin installationCheck your WordPress plugins directory (wp-content/plugins/) for a folder named 'cp-contact-form-with-paypal' or similar variant. If using WordPress admin, go to Plugins > Installed Plugins and look for 'CP Contact Form With Paypal' or 'Codepeople Cp Contact Form With Paypal'.Affected if The plugin folder exists in your WordPress installation.
-
Determine the installed plugin versionIn WordPress admin, click on the plugin name to view its details, or open the main plugin PHP file (usually cp-contactformpp.php) and look for a version comment/constant at the top. Compare this version number to 1.1.6.Affected if The installed version is lower than 1.1.6 (for example, 1.1.5, 1.1.4, 1.0.x, etc.).
-
Verify vulnerable files existIn the plugin folder, confirm that cp_contactformpp.php and/or cp_contactformpp_admin_int_list.inc.php are present. These files handle form submissions and admin interface logic.Affected if These specific files exist in the plugin directory, indicating the vulnerable code is present.
-
Check if admin access is availableLog into WordPress admin panel and navigate to the plugin settings page (usually under Settings or a dedicated CP Contact Form menu). Determine if you can access the form configuration and submission list.Affected if You have admin access to configure the plugin forms, which means the stored XSS attack vector through CSRF is potentially exploitable in your environment.
You are affected if the CP Contact Form with PayPal plugin is installed with any version lower than 1.1.6 and the vulnerable PHP files are present.
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 data1.1.6
Update the plugin to version 1.1.6 or later, which includes proper CSRF token validation and input sanitization to prevent cross-site scripting attacks.
Fix this in Cp Contact Form With Paypal
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9233 — 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-2015-9233 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