CVE-2026-6627: CWE-862 Missing Authorization in saadiqbal WPFormify – Stripe Payments with Form and Checkout
The WPFormify – Stripe Payments with Form and Checkout WordPress plugin up to version 1.1.1 contains a missing authorization vulnerability. This flaw allows unauthenticated attackers to modify or delete Stripe payment credentials due to missing capability checks and nonce verification in certain admin functions. The vulnerability arises because these functions are hooked to admin_init, which can be accessed without authentication via admin-post.php. Exploitation can lead to redirecting payments to attacker-controlled Stripe accounts or disabling the Stripe integration by deleting credentials.
AI Analysis
Technical Summary
CVE-2026-6627 is a missing authorization vulnerability (CWE-862) in the WPFormify – Stripe Payments with Form and Checkout WordPress plugin affecting all versions up to and including 1.1.1. The issue stems from the lack of capability checks and nonce verification in the wpf_stripe_callback_success() and wpf_stripe_disconnect() functions, both hooked to admin_init. Since admin_init is triggered on admin-post.php, which is accessible without authentication, unauthenticated attackers can invoke these functions to overwrite the site's Stripe API credentials with attacker-controlled values or disconnect the Stripe integration by deleting stored credentials. This can result in payments being redirected to the attacker’s Stripe account or loss of payment functionality.
Potential Impact
An unauthenticated attacker can overwrite the Stripe API credentials used by the site, redirecting payments to their own Stripe account, causing financial loss or fraud. Alternatively, the attacker can delete the stored Stripe credentials, disrupting payment processing on the site. The vulnerability does not impact confidentiality but has a high integrity impact and a low availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to admin-post.php and monitor for suspicious requests targeting the vulnerable plugin endpoints. Applying capability checks and nonce verification in the affected functions is necessary to prevent unauthorized access.
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 WordPress plugin up to version 1.1.1 contains a missing authorization vulnerability. This flaw allows unauthenticated attackers to modify or delete Stripe payment credentials due to missing capability checks and nonce verification in certain admin functions. The vulnerability arises because these functions are hooked to admin_init, which can be accessed without authentication via admin-post.php. Exploitation can lead to redirecting payments to attacker-controlled Stripe accounts or disabling the Stripe integration by deleting credentials.
CVSS v3.1
Score 8.2high
Affected software
saadiqbal
WPFormify – Stripe Payments with Form and Checkout
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-6627 is a missing authorization vulnerability (CWE-862) in the WPFormify – Stripe Payments with Form and Checkout WordPress plugin affecting all versions up to and including 1.1.1. The issue stems from the lack of capability checks and nonce verification in the wpf_stripe_callback_success() and wpf_stripe_disconnect() functions, both hooked to admin_init. Since admin_init is triggered on admin-post.php, which is accessible without authentication, unauthenticated attackers can invoke these functions to overwrite the site's Stripe API credentials with attacker-controlled values or disconnect the Stripe integration by deleting stored credentials. This can result in payments being redirected to the attacker’s Stripe account or loss of payment functionality.
Potential Impact
An unauthenticated attacker can overwrite the Stripe API credentials used by the site, redirecting payments to their own Stripe account, causing financial loss or fraud. Alternatively, the attacker can delete the stored Stripe credentials, disrupting payment processing on the site. The vulnerability does not impact confidentiality but has a high integrity impact and a low availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to admin-post.php and monitor for suspicious requests targeting the vulnerable plugin endpoints. Applying capability checks and nonce verification in the affected functions is necessary to prevent unauthorized access.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-04-19T16:45:33.413Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a72e5c9bf8831d539735134
Added to database: 08/05/2026, 07:27:05 UTC
Last enriched: 08/12/2026, 15:37:35 UTC
Last updated: 09/18/2026, 02:27:51 UTC
Views: 37
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.