Strategic Overview
- Status
- Patched in 1.1.2
- Affected Plugin
- WPFormify – Stripe Payments with Form and Checkout
- Affected Version
<= 1.1.1- CVSS
- 8.2High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-6627
At a glance
CVE-2026-6627 is a high-severity Missing Authorization vulnerability in the WPFormify WordPress plugin, affecting versions <= 1.1.1. It carries a CVSS score of 8.2 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.1.2; sites on affected versions should update now. Disclosed August 2026, reported by Legion Hunter.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-862: Missing Authorization
WPFormify <= 1.1.1 carries this weakness at wpf_stripe_callback_success(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WPFormify the fix is 1.1.2: builds <= 1.1.1 are affected, anything from 1.1.2 onward is not.
Remediation
Update to version 1.1.2, or a newer patched version
How WordSec helps
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WPFormify 1.1.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C