Paypal \& Stripe Add OnWordPress extension · Wpplugin

CVE-2023-24405

HIGH · 8.8 CVSS v3.1 Published 2023-07-10

Fix available

A fix is available. Upgrade to 1.9.4 or later.

See remediation →

95/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

Cross-Site Request Forgery (CSRF) vulnerability in Scott Paterson Contact Form 7 – PayPal & Stripe Add-on plugin <= 1.9.3 versions.

Technical summary

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Contact Form 7 – PayPal & Stripe Add-on plugin for WordPress (versions 1.9.3 and below). The plugin fails to properly validate the origin of requests, allowing attackers to trick authenticated administrators into unknowingly submitting malicious requests that could modify payment settings or trigger unintended PayPal/Stripe transactions.

MitigationUpdate to the latest version of the plugin which implements anti-CSRF tokens (synchronizer tokens) for state-changing operations. As a temporary measure, enforce SameSite cookie attributes and validate Origin/Referer headers on server-side form handlers.

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

Affected products & versions

NVD · CPE data

Paypal \& Stripe Add OnWordPress extension

Affected:< 1.9.4

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check plugin version

In WordPress admin, go to Plugins > Contact Form 7 - PayPal & Stripe Add-on and view the version number, or check the plugin files in wp-content/plugins/ for the version in the main PHP file or readme.txt

Affected if The installed version is below 1.9.4 (versions 1.9.3 and below are affected)
Verify plugin is active

Confirm the Contact Form 7 - PayPal & Stripe Add-on plugin is enabled in the WordPress plugins list

Affected if The plugin is active and the version is below 1.9.4
Confirm payment integration exists

Check if the plugin has PayPal or Stripe settings configured under the plugin settings page or in wp_options table for option names containing 'paypal' or 'stripe'

Affected if Payment settings exist and the plugin version is below 1.9.4 - this makes the CSRF impact more severe as attackers could modify real payment configurations

A WordPress site is affected if the Contact Form 7 - PayPal & Stripe Add-on plugin is installed and active with a version number lower than 1.9.4, regardless of specific configuration, since the CSRF flaw exists in the plugin's request handling logic.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.9.4 or later

Fixed in 1.9.4

Interim mitigation

Update to the latest version of the plugin which implements anti-CSRF tokens (synchronizer tokens) for state-changing operations. As a temporary measure, enforce SameSite cookie attributes and validate Origin/Referer headers on server-side form handlers.

Recommended fix Moderate confidence

1.9.4

Log in to the WordPress admin dashboard
Navigate to Plugins > Installed Plugins
Locate the 'Contact Form 7 – PayPal & Stripe Add-on' plugin
Check the current version number to confirm it is below 1.9.4
Click 'Update now' if an update to version 1.9.4 or higher is available
Alternatively, download version 1.9.4 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
After updating, verify the new version number in the Plugins list

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

Fix this in Paypal \& Stripe Add On Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.comThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-24405 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2023-24405?

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.

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

At a glance

A fix existsUpgrade to 1.9.4 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Paypal \& Stripe Add On

Remediation

A high-priority fix

Fix this in Paypal \& Stripe Add On 9 hrs · Moderate

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2023-24405 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References