Is Contact Form 7 safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.5.3). As of 2026-11-04. 7 issues are on record for older versions; version 2.5.2 or newer fixes all of them that state a fix. Keep Contact Form 7 on the latest version (2.5.3) and remove it if you do not use it.

Which versions of Contact Form 7 are vulnerable?

Known issues on record (newest first): Missing authorization check (2.5.1 and older, fixed in 2.5.2); Security issue (2.4.9 and older, fixed in 2.4.10); Stored cross-site scripting (XSS) (2.3.4 and older, fixed in 2.4.1); Reflected cross-site scripting (XSS) (2.3.1 and older, fixed in 2.3.2); Reflected cross-site scripting (XSS) (2.3 and older, fixed in 2.3.1); Reflected cross-site scripting (XSS) (2.0 and older, fixed in 2.1). The full list with sources is on this page.

What is the latest version of Contact Form 7?

2.5.3, according to wordpress.org (last updated 2026-10-07). It has 7,000+ active installs.

What should I do if my Contact Form 7 is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update contact-form-7-paypal-add-on). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · contact-form-7-paypal-add-on · data as of 2026-11-04

Is Contact Form 7 safe? Known vulnerabilities and latest version

Latest version: 2.5.3
Last updated: 2026-10-07
Active installs: 7,000+
Known issues on record: 7
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 5.5+

Easily add PayPal and Stripe to Contact Form 7. Accept credit card payments with Stripe & PayPal on your site today. Offical PayPal & Stripe Partner. — by Scott Paterson

What to do

Update to the latest version (2.5.3). Anything older than 2.5.2 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get contact-form-7-paypal-add-on --field=version shows what you run; wp plugin update contact-form-7-paypal-add-on updates it.

Check your version

Known vulnerabilities

7 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.5 CVE-2026-66660 · published 2026-08-13

Missing authorization check in Contact Form 7 (2.5.1 and older)

Affected: 2.5.1 and older
Fixed in: 2.5.2 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unauthenticated Broken Access Control in Contact Form 7 – PayPal & Stripe Add-on <= 2.5.1 versions.

NVD CVE-2026-66660 Patchstack advisory

medium 5.3 CVE-2026-9189 · published 2026-05-29

Security issue in Contact Form 7 (2.4.9 and older)

Affected: 2.4.9 and older
Fixed in: 2.4.10 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Contact Form 7 – PayPal & Stripe Add-on plugin for WordPress is vulnerable to Payment Bypass via Insufficient Verification of Data Authenticity in all versions up to, and including, 2.4.9. Although `cf7pp_paypal_ipn_handler()` correctly validates IPN authenticity by posting back to PayPal with `cmd=_notify-validate`, it fails to compare the IPN payload's `mc_gross` (payment amount), `mc_currency`, or `receiver_email` fields against the corresponding stored order values before passing the attacker-controlled `invoice` field directly to `cf7pp_complete_payment()`, which marks the order completed after only an integer cast with no amount verification. This makes it possible for unauthenticated attackers to mark arbitrary high-value pending orders as fully paid by making a minimal real PayPal payment and crafting an IPN whose `invoice` parameter references the targeted order, effectively completing purchases without tendering the required payment amount.

NVD CVE-2026-9189 Wordfence advisory Code change (fix)Plugin source

medium 5.9 CVE-2025-47518 · published 2025-05-07

Stored cross-site scripting (XSS) in Contact Form 7 (2.3.4 and older)

Affected: 2.3.4 and older
Fixed in: 2.4.1
Access needed (per CVSS): Needs an admin-level account; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Scott Paterson Contact Form 7 – PayPal & Stripe Add-on contact-form-7-paypal-add-on allows Stored XSS.This issue affects Contact Form 7 – PayPal & Stripe Add-on: from n/a through <= 2.3.4.

NVD CVE-2025-47518 Patchstack advisory

medium 6.1 CVE-2024-10683 · published 2024-11-09

Reflected cross-site scripting (XSS) in Contact Form 7 (2.3.1 and older)

Affected: 2.3.1 and older
Fixed in: 2.3.2 *
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Contact Form 7 – PayPal & Stripe Add-on plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg & remove_query_arg without appropriate escaping on the URL in all versions up to, and including, 2.3.1. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. This is only exploitable when the leave a review notice is present in the dashboard.

NVD CVE-2024-10683 Wordfence advisory Code change (fix)Plugin source

high 7.1 CVE-2024-48021 · published 2024-10-17

Reflected cross-site scripting (XSS) in Contact Form 7 (2.3 and older)

Affected: 2.3 and older
Fixed in: 2.3.1
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Scott Paterson Contact Form 7 – PayPal & Stripe Add-on contact-form-7-paypal-add-on allows Reflected XSS.This issue affects Contact Form 7 – PayPal & Stripe Add-on: from n/a through <= 2.3.

NVD CVE-2024-48021 Patchstack advisory

medium 6.1 CVE-2024-29130 · published 2024-03-19

Reflected cross-site scripting (XSS) in Contact Form 7 (2.0 and older)

Affected: 2.0 and older
Fixed in: 2.1
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper 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.

NVD CVE-2024-29130 Patchstack advisory

high 8.8 CVE-2023-24405 · published 2023-07-10

Cross-site request forgery (CSRF) in Contact Form 7 (1.9.3 and older)

Affected: 1.9.3 and older
Fixed in: 1.9.4
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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

NVD CVE-2023-24405 Patchstack advisory

Recent activity

2026-10-07 — latest release on wordpress.org (2.5.3).
2026-08-13 — Missing authorization check disclosed (CVE-2026-66660), fixed in 2.5.2.
2026-05-29 — Security issue disclosed (CVE-2026-9189), fixed in 2.4.10.
2025-05-07 — Stored cross-site scripting (XSS) disclosed (CVE-2025-47518), fixed in 2.4.1.

Free. We check the CVE feeds every day and email you only when a new issue for Contact Form 7 (contact-form-7-paypal-add-on) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (4) · Missing authorization (1) · Cross-site request forgery (CSRF) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/contact-form-7-paypal-add-on (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/contact-form-7-paypal-add-on"><img src="https://laskyr.com/plugins/contact-form-7-paypal-add-on/badge.svg" alt="Contact Form 7 vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Contact Form 7 safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (2.5.3)

What to do

Check your version

Known vulnerabilities

Missing authorization check in Contact Form 7 (2.5.1 and older)

Security issue in Contact Form 7 (2.4.9 and older)

Stored cross-site scripting (XSS) in Contact Form 7 (2.3.4 and older)

Reflected cross-site scripting (XSS) in Contact Form 7 (2.3.1 and older)

Reflected cross-site scripting (XSS) in Contact Form 7 (2.3 and older)

Reflected cross-site scripting (XSS) in Contact Form 7 (2.0 and older)

Cross-site request forgery (CSRF) in Contact Form 7 (1.9.3 and older)

Recent activity

Get an email when Contact Form 7 has a new vulnerability

Browse vulnerabilities

Where this data comes from