dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13384

HIGH · 7.5 CVSS v3.1 Published 2025-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 CP Contact Form with PayPal plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.3.56. This is due to the plugin exposing an unauthenticated IPN-like endpoint (via the 'cp_contactformpp_ipncheck' query parameter) that processes payment confirmations without any authentication, nonce verification, or PayPal IPN signature validation. This makes it possible for unauthenticated attackers to mark form submissions as paid without making actual payments by sending forged payment notification requests with arbitrary POST data (payment_status, txn_id, payer_email).

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 confidence

The CP Contact Form with PayPal WordPress plugin versions up to 1.3.56 contains an unauthenticated IPN endpoint accessible via the 'cp_contactformpp_ipncheck' query parameter that processes payment confirmations without any authentication, nonce verification, or PayPal IPN signature validation, allowing attackers to forge payment notifications and mark submissions as paid without actual payment.

MitigationUpdate the plugin to the latest version and ensure PayPal IPN signature validation is properly implemented to verify authenticity of payment notifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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

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. Confirm plugin installation
    Check if the CP Contact Form with PayPal plugin is present in the WordPress plugins directory (wp-content/plugins/) or list installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin 'CP Contact Form with PayPal' is installed and active on the site
  2. Check installed version
    View the plugin version in the plugin header (typically in the main PHP file or readme.txt in the plugin directory) or check via WordPress admin plugin list
    Affected if The installed version is 1.3.56 or any earlier version (the vulnerability affects versions up to and including 1.3.56)
  3. Identify the IPN endpoint
    Examine the plugin files for the 'cp_contactformpp_ipncheck' query parameter handling - search plugin source code for this parameter name to locate the IPN handler
    Affected if The plugin code contains a handler for 'cp_contactformpp_ipncheck' that processes requests without authentication checks
  4. Check IPN validation configuration
    Review the plugin settings in WordPress admin (CP Contact Form with PayPal settings page) for any PayPal IPN signature validation option and verify if it is enabled
    Affected if PayPal IPN signature validation is disabled, not configured, or the option is missing from the plugin settings

A site is affected if the CP Contact Form with PayPal plugin version 1.3.56 or earlier is installed with the unauthenticated IPN endpoint accessible and PayPal IPN signature validation disabled or not implemented.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version and ensure PayPal IPN signature validation is properly implemented to verify authenticity of payment notifications.

Recommended fix Moderate confidence

Update to the latest version of CP Contact Form with PayPal (version 1.3.57 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'CP Contact Form with PayPal' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update was successful by checking the plugin version after updating
  6. 6. Test the PayPal integration to ensure payments are still processed correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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