Plugins · wpformify · data as of 2026-11-04
Is WPFormify safe? Known vulnerabilities and latest version
- Latest version
- 1.1.2
- Last updated
- 2026-06-02
- Active installs
- 10+
- Known issues on record
- 1
- Unpatched in latest
- 0
- Tested up to WP
- 7.0.8 · PHP 5.5+
In a few simple steps you can start accepting credit card payments with Stripe Checkout on your WordPress site. — by Saad Iqbal
What to do
- Update to the latest version (1.1.2). Anything older than 1.1.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 wpformify --field=version shows what you run; wp plugin update wpformify updates it.
Check your version
Known vulnerabilities
1 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.
high 8.2 CVE-2026-6627 · published 2026-08-05
Missing authorization check in WPFormify (1.1.1 and older)
- Affected
- 1.1.1 and older
- Fixed in
- 1.1.2 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The WPFormify – Stripe Payments with Form and Checkout plugin for WordPress is vulnerable to unauthorized modification and deletion of Stripe payment credentials in all versions up to, and including, 1.1.1. This is due to missing capability checks and nonce verification on the `wpf_stripe_callback_success()` and `wpf_stripe_disconnect()` functions, both hooked to `admin_init`. The `admin_init` hook fires on `admin-post.php` which is accessible without authentication. This makes it possible for unauthenticated attackers to overwrite the site's Stripe API credentials with attacker-controlled values (redirecting payments to the attacker's Stripe account) or disconnect the Stripe integration entirely by deleting the stored credentials.
NVD CVE-2026-6627Wordfence advisoryCode change (fix)Plugin source
Recent activity
- 2026-06-02 — latest release on wordpress.org (1.1.2).
- 2026-08-05 — Missing authorization check disclosed (CVE-2026-6627), fixed in 1.1.2.
Get an email when WPFormify has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for WPFormify (wpformify) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by Saad Iqbal (16 tracked)
Types found in this plugin: Missing authorization (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/wpformify (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/wpformify"><img src="https://laskyr.com/plugins/wpformify/badge.svg" alt="WPFormify vulnerability status"></a>