<?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>Fri, 02 Oct 2026 15:01:27 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-16947</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-16947</link>
      <description>&lt;p&gt;The Total processing card payments for WooCommerce WordPress plugin through 7.3 does not validate a user-supplied path before using it to build a server-side verification request, and does not verify the authenticity of the response, allowing unauthenticated attackers to redirect that request to an arbitrary host (disclosing the merchant&amp;#39;s payment-gateway credentials) and to forge a success response that marks arbitrary WooCommerce orders as paid.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Total processing card payments for WooCommerce WordPress plugin through 7.3 does not validate a user-supplied path before using it to build a server-side verification request, and does not verify the authenticity of the response, allowing unauthenticated attackers to redirect that request to an arbitrary host (disclosing the merchant&amp;#39;s payment-gateway credentials) and to forge a success response that marks arbitrary WooCommerce orders as paid.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-16947</guid>
    </item>
    <item>
      <title>GHSA-675h-pw44-fcfq</title>
      <link>https://db.gcve.eu/vuln/ghsa-675h-pw44-fcfq</link>
      <description>&lt;p&gt;The Total processing card payments for WooCommerce WordPress plugin through 7.3 does not validate a user-supplied path before using it to build a server-side verification request, and does not verify the authenticity of the response, allowing unauthenticated attackers to redirect that request to an arbitrary host (disclosing the merchant&amp;#39;s payment-gateway credentials) and to forge a success response that marks arbitrary WooCommerce orders as paid.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Total processing card payments for WooCommerce WordPress plugin through 7.3 does not validate a user-supplied path before using it to build a server-side verification request, and does not verify the authenticity of the response, allowing unauthenticated attackers to redirect that request to an arbitrary host (disclosing the merchant&amp;#39;s payment-gateway credentials) and to forge a success response that marks arbitrary WooCommerce orders as paid.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-675h-pw44-fcfq</guid>
    </item>
  </channel>
</rss>
