CVE-2026-6627: CWE-862 Missing Authorization in saadiqbal WPFormify – Stripe Payments with Form and Checkout
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.
AI Analysis
Technical Summary
CVE-2026-6627 describes a missing authorization vulnerability (CWE-862) in the WPFormify – Stripe Payments with Form and Checkout plugin for WordPress, affecting all versions up to and including 1.1.1. The vulnerability arises because the functions `wpf_stripe_callback_success()` and `wpf_stripe_disconnect()`, which handle Stripe payment credential updates and disconnections, lack proper capability checks and nonce verification. These functions are hooked to the `admin_init` action, which is triggered on `admin-post.php`, a URL accessible without authentication. As a result, unauthenticated attackers can overwrite the site's Stripe API credentials with attacker-controlled values or delete the stored credentials, potentially redirecting payments or disabling Stripe payment functionality.
Potential Impact
The vulnerability allows unauthenticated attackers to modify or delete Stripe payment credentials used by the site. This can lead to payments being redirected to attacker-controlled Stripe accounts, causing financial loss or fraud. Additionally, attackers can disconnect the Stripe integration entirely, disrupting payment processing on the affected site.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to `admin-post.php` where possible and monitor for suspicious activity related to Stripe credential changes. Avoid exposing the plugin's admin endpoints to unauthenticated users.
CVE-2026-6627: CWE-862 Missing Authorization in saadiqbal WPFormify – Stripe Payments with Form and Checkout
Description
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.
CVSS v3.1
Score 8.2high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-6627 describes a missing authorization vulnerability (CWE-862) in the WPFormify – Stripe Payments with Form and Checkout plugin for WordPress, affecting all versions up to and including 1.1.1. The vulnerability arises because the functions `wpf_stripe_callback_success()` and `wpf_stripe_disconnect()`, which handle Stripe payment credential updates and disconnections, lack proper capability checks and nonce verification. These functions are hooked to the `admin_init` action, which is triggered on `admin-post.php`, a URL accessible without authentication. As a result, unauthenticated attackers can overwrite the site's Stripe API credentials with attacker-controlled values or delete the stored credentials, potentially redirecting payments or disabling Stripe payment functionality.
Potential Impact
The vulnerability allows unauthenticated attackers to modify or delete Stripe payment credentials used by the site. This can lead to payments being redirected to attacker-controlled Stripe accounts, causing financial loss or fraud. Additionally, attackers can disconnect the Stripe integration entirely, disrupting payment processing on the affected site.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to `admin-post.php` where possible and monitor for suspicious activity related to Stripe credential changes. Avoid exposing the plugin's admin endpoints to unauthenticated users.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-04-19T16:45:33.413Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a72e5c9bf8831d539735134
Added to database: 08/05/2026, 07:27:05 UTC
Last enriched: 08/05/2026, 07:43:31 UTC
Last updated: 08/06/2026, 02:07:11 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.