dbcve.org
Paypal ProWordPress extension · Ithemes

CVE-2020-14092

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-02
Fix available
A fix is available. Upgrade to 1.1.65 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges 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
The CodePeople Payment Form for PayPal Pro plugin before 1.1.65 for WordPress allows SQL Injection.

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 SQL Injection vulnerability exists in the CodePeople Payment Form for PayPal Pro WordPress plugin in versions prior to 1.1.65. The vulnerability allows remote attackers to inject malicious SQL queries through unsanitized input fields within the plugin, potentially enabling data exfiltration or complete database compromise.

MitigationUpdate the CodePeople Payment Form for PayPal Pro plugin to version 1.1.65 or later to remediate the SQL Injection vulnerability. If immediate updating is not feasible, consider disabling the plugin until the patch can be applied.

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
Paypal ProWordPress extension
Affected:< 1.1.65

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the plugin installation directory
    Browse to the WordPress plugins folder (typically /wp-content/plugins/) and look for directories containing 'paypal-pro', 'codepeople', or 'ithemes' in the name. Common folder names may include 'cp-pp', 'paypal-pro', or similar variations.
    Affected if The plugin directory exists in the WordPress installation
  2. Read the plugin version metadata
    Open the main plugin PHP file (usually named plugin-name.php or with the same name as the directory) and locate the plugin header comment containing 'Version:' information. Alternatively, check the readme.txt file in the plugin directory for the version field.
    Affected if The version listed is below 1.1.65 (for example, 1.1.64, 1.0.5, etc.)
  3. Verify the plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and check if the CodePeople Payment Form for PayPal Pro or Ithemes Paypal Pro plugin is activated. Alternatively, query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin appears in the list of active plugins
  4. Confirm vulnerability applicability
    The SQL injection vulnerability is present in the plugin code itself when handling form input fields. No specific module or feature toggle is required - the flaw exists in how the plugin processes user-submitted data in PayPal Pro payment forms.
    Affected if The plugin version is vulnerable AND the plugin is actively running on the WordPress site

A user is affected if the CodePeople Payment Form for PayPal Pro (or Ithemes Paypal Pro) plugin is installed with a version lower than 1.1.65 and the plugin is currently active on the WordPress site.

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.1.65 or later
Fixed in 1.1.65
Interim mitigation

Update the CodePeople Payment Form for PayPal Pro plugin to version 1.1.65 or later to remediate the SQL Injection vulnerability. If immediate updating is not feasible, consider disabling the plugin until the patch can be applied.

Recommended fix High confidence

1.1.65

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'CodePeople Payment Form for PayPal Pro' in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 1.1.65 or later
  5. Verify the update completed successfully
  6. Consider backing up the site before updating

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

Fix this in Paypal Pro Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14092 — 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-2020-14092 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