Cp Contact Form With PaypalWordPress extension · Cfpaypal
CVE-2015-9234
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 SQL injection via the cp_contactformpp_id parameter to cp_contactformpp.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 confidenceSQL injection vulnerability in the CP Contact Form with PayPal WordPress plugin allows attackers to inject malicious SQL queries through the cp_contactformpp_id parameter in cp_contactformpp.php, potentially exposing or manipulating the underlying database.
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.5CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the CP Contact Form with PayPal plugin is installedCheck your WordPress plugins directory for a folder named 'cp-contact-form-with-paypal' or similar, and list its contents to confirm the presence of cp_contactformpp.phpAffected if The plugin folder and cp_contactformpp.php file exist in the WordPress plugins directory
-
Determine the installed plugin versionOpen the main plugin file (typically the primary PHP file in the plugin folder) and look for a version comment or constant at the top of the file, or check the plugin header in readme.txtAffected if The version number found is 1.1.5 or lower
-
Locate and inspect the vulnerable fileFind cp_contactformpp.php within the plugin directory and verify it contains code that processes the cp_contactformpp_id parameter, typically via $_REQUEST or $_GETAffected if The file exists and contains handling of the cp_contactformpp_id parameter without visible sanitization functions
-
Verify the vulnerable code patternSearch within cp_contactformpp.php for direct use of the cp_contactformpp_id parameter in SQL queries, looking for patterns like query construction without prepared statements or escapingAffected if The parameter is used in SQL queries without proper sanitization or prepared statements
-
Check if the affected endpoint is accessibleAttempt to access the cp_contactformpp.php file directly via HTTP request with a test cp_contactformpp_id value to see if the parameter is processedAffected if The file responds to requests and processes the cp_contactformpp_id parameter without validation
You are affected if the CP Contact Form with PayPal plugin version is 1.1.5 or lower and the cp_contactformpp.php file processes the cp_contactformpp_id parameter in SQL queries without sanitization.
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 dataUpgrade the CP Contact Form with PayPal plugin to version 1.1.6 or later to obtain the patched code with proper input sanitization for the cp_contactformpp_id parameter.
Fix this in Cp Contact Form With Paypal
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.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-9234 — 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-9234 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