<?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>Mon, 09 Nov 2026 04:14:47 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-119213</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-119213</link>
      <description>&lt;p&gt;The Fluent Support – Helpdesk &amp;amp; Customer Support Ticket System plugin for WordPress is vulnerable to unauthenticated modification of a linked customer&amp;#39;s stored profile fields in versions up to, and including, 2.4.7 Its first-party Fluent Forms integration (FeedIntegration::notify()) opens a ticket from each public form submission and, for a logged-out submitter, resolves the submitted email to an existing WordPress account via get_user_by(&amp;#39;email&amp;#39;, ...) without verifying the submitter controls that address, then passes the attacker-supplied data to Customer::maybeCreateCustomer(). This makes it possible for unauthenticated attackers to overwrite a limited set of a registered customer&amp;#39;s stored profile fields where an administrator has enabled a FluentSupport feed on a public form. The email address, role and status are never changed; first and last name are overwritten only when the target user has no name set in user meta; and other fields (title, address, city, state, zip, country) are writable only where an administrator has mapped them in the feed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Fluent Support – Helpdesk &amp;amp; Customer Support Ticket System plugin for WordPress is vulnerable to unauthenticated modification of a linked customer&amp;#39;s stored profile fields in versions up to, and including, 2.4.7 Its first-party Fluent Forms integration (FeedIntegration::notify()) opens a ticket from each public form submission and, for a logged-out submitter, resolves the submitted email to an existing WordPress account via get_user_by(&amp;#39;email&amp;#39;, ...) without verifying the submitter controls that address, then passes the attacker-supplied data to Customer::maybeCreateCustomer(). This makes it possible for unauthenticated attackers to overwrite a limited set of a registered customer&amp;#39;s stored profile fields where an administrator has enabled a FluentSupport feed on a public form. The email address, role and status are never changed; first and last name are overwritten only when the target user has no name set in user meta; and other fields (title, address, city, state, zip, country) are writable only where an administrator has mapped them in the feed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-119213</guid>
    </item>
    <item>
      <title>GHSA-q7x6-x924-p7cg</title>
      <link>https://db.gcve.eu/vuln/ghsa-q7x6-x924-p7cg</link>
      <description>&lt;p&gt;The Fluent Support – Helpdesk &amp;amp; Customer Support Ticket System plugin for WordPress is vulnerable to unauthenticated modification of a linked customer&amp;#39;s stored profile fields in versions up to, and including, 2.4.7 Its first-party Fluent Forms integration (FeedIntegration::notify()) opens a ticket from each public form submission and, for a logged-out submitter, resolves the submitted email to an existing WordPress account via get_user_by(&amp;#39;email&amp;#39;, ...) without verifying the submitter controls that address, then passes the attacker-supplied data to Customer::maybeCreateCustomer(). This makes it possible for unauthenticated attackers to overwrite a limited set of a registered customer&amp;#39;s stored profile fields where an administrator has enabled a FluentSupport feed on a public form. The email address, role and status are never changed; first and last name are overwritten only when the target user has no name set in user meta; and other fields (title, address, city, state, zip, country) are writable only where an administrator has mapped them in the feed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Fluent Support – Helpdesk &amp;amp; Customer Support Ticket System plugin for WordPress is vulnerable to unauthenticated modification of a linked customer&amp;#39;s stored profile fields in versions up to, and including, 2.4.7 Its first-party Fluent Forms integration (FeedIntegration::notify()) opens a ticket from each public form submission and, for a logged-out submitter, resolves the submitted email to an existing WordPress account via get_user_by(&amp;#39;email&amp;#39;, ...) without verifying the submitter controls that address, then passes the attacker-supplied data to Customer::maybeCreateCustomer(). This makes it possible for unauthenticated attackers to overwrite a limited set of a registered customer&amp;#39;s stored profile fields where an administrator has enabled a FluentSupport feed on a public form. The email address, role and status are never changed; first and last name are overwritten only when the target user has no name set in user meta; and other fields (title, address, city, state, zip, country) are writable only where an administrator has mapped them in the feed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-q7x6-x924-p7cg</guid>
    </item>
  </channel>
</rss>
