<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 06:28:25 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-6627</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-6627</link>
      <description>&lt;p&gt;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&amp;#39;s Stripe API credentials with attacker-controlled values (redirecting payments to the attacker&amp;#39;s Stripe account) or disconnect the Stripe integration entirely by deleting the stored credentials.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;s Stripe API credentials with attacker-controlled values (redirecting payments to the attacker&amp;#39;s Stripe account) or disconnect the Stripe integration entirely by deleting the stored credentials.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-6627</guid>
    </item>
    <item>
      <title>GHSA-hww4-pj88-89c3</title>
      <link>https://db.gcve.eu/vuln/ghsa-hww4-pj88-89c3</link>
      <description>&lt;p&gt;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&amp;#39;s Stripe API credentials with attacker-controlled values (redirecting payments to the attacker&amp;#39;s Stripe account) or disconnect the Stripe integration entirely by deleting the stored credentials.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;s Stripe API credentials with attacker-controlled values (redirecting payments to the attacker&amp;#39;s Stripe account) or disconnect the Stripe integration entirely by deleting the stored credentials.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-hww4-pj88-89c3</guid>
    </item>
  </channel>
</rss>
