CVE-2026-6627
Unauthenticated attackers can overwrite or delete Stripe credentials in WPFormify plugin.
Is CVE-2026-6627 being exploited?
Not confirmed. CVE-2026-6627 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.
How severe is CVE-2026-6627?
CVE-2026-6627 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-6627?
Yes. A fix has been recorded for CVE-2026-6627. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-6627 affect?
CVE-2026-6627 affects WPFormify – Stripe Payments with Form and Checkout <= 1.1.1, WordPress (admin-post.php endpoint). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-6627?
Update plugin to fixed version (>1.1.1), rotate Stripe keys, restrict admin-post.php access
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can overwrite Stripe API keys to redirect payments or delete credentials, disrupting payments and enabling fraud.
Immediate action required
- affected<= 1.1.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.