Paypal \& Stripe Add OnWordPress extension · Wpplugin
CVE-2024-29130
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Scott Paterson Contact Form 7 – PayPal & Stripe Add-on allows Reflected XSS.This issue affects Contact Form 7 – PayPal & Stripe Add-on: from n/a through 2.0.
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 confidenceReflected XSS vulnerability in the Contact Form 7 – PayPal & Stripe Add-on plugin allows attackers to inject malicious scripts via unsanitized user input that gets reflected in the web page without proper output encoding.
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 \& Stripe Add OnWordPress extension
< 2.1CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationCheck if the Contact Form 7 - PayPal & Stripe Add-on plugin is installed in your WordPress environment by reviewing the plugins list in wp-admin or inspecting the plugins directoryAffected if the plugin appears in your installed plugins list
-
Identify installed versionLocate the plugin version number in the WordPress plugin administration panel or check the plugin header in its main PHP file (typically named similar to paypal-stripe-addon.php)Affected if the version number is lower than 2.1 (e.g., 2.0, 1.x)
-
Confirm active contact formsReview your active contact forms that use the PayPal or Stripe integration to determine if they accept and display user-submitted dataAffected if you have contact forms with PayPal/Stripe add-on active that accept user input
-
Check for reflected user inputSubmit test input through affected forms and inspect the resulting page source or rendered output to see if your input is reflected back without proper encodingAffected if user-submitted data appears in the output without HTML entity encoding (e.g., <script> tags render as literal text rather than being escaped)
You are affected if the Contact Form 7 - PayPal & Stripe Add-on plugin is installed at version less than 2.1 and you have active forms that reflect user input without proper encoding.
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.
dbcve · scoped2.1
Apply proper input validation and output encoding using WordPress escaping functions (esc_html, esc_attr, esc_url, etc.) to all user-controlled data before rendering in HTML pages.
Version 2.1
- Back up your WordPress site before making any changes
- Update the Contact Form 7 – PayPal & Stripe Add-on plugin to version 2.1 or later via the WordPress plugin management interface
- Verify the update was successfully applied by checking the installed version number
- Consider testing the payment integration functionality after the update to ensure proper operation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Paypal \& Stripe Add On
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29130 — 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-2024-29130 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