<?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, 16 Oct 2026 19:54:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-104749 — Bit integrations &lt;= 2.10.6 - Unauthenticated Privilege Escalation via Identity-Confused Log Re-execution to Account Tak…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-104749</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; bitpressadmin Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS &amp;amp; Email Automation&lt;/p&gt;
&lt;p&gt;The Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS &amp;amp; Email Automation plugin for WordPress is vulnerable to Privilege Escalation via Log Re-execution in all versions up to, and including, 2.10.6 The vulnerability exists because `IntegrationHandler::executeWithCapture()` stores raw, attacker-controlled field values — including `user_pass` and `user_email` — verbatim into `wp_btcbi_log.field_data` on anonymous front-end requests with no capability check, and `LogHandler::reexecute()` feeds that stored payload back through `Flow::execute()` inside the replaying administrator&amp;#39;s session without validating the identity that originally produced the data, causing `RegistrationController::updateUser()` to resolve the target user ID to the administrator and write the attacker-supplied password via `wp_update_user()`. This makes it possible for unauthenticated attackers to overwrite the administrator&amp;#39;s password and fully take over the administrator account. Exploitation requires that an administrator has configured a flow mapping a user-supplied form field to the `user_pass` parameter of the WP User Registration &amp;#34;Update User&amp;#34; action, and that the administrator subsequently clicks &amp;#34;Re-execute&amp;#34; on the failure log row produced by the anonymous submission from the plugin&amp;#39;s log screen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; bitpressadmin Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS &amp;amp; Email Automation&lt;/p&gt;
&lt;p&gt;The Bit integrations – Form Integration, Webhook, Spreadsheets, CRM, LMS &amp;amp; Email Automation plugin for WordPress is vulnerable to Privilege Escalation via Log Re-execution in all versions up to, and including, 2.10.6 The vulnerability exists because `IntegrationHandler::executeWithCapture()` stores raw, attacker-controlled field values — including `user_pass` and `user_email` — verbatim into `wp_btcbi_log.field_data` on anonymous front-end requests with no capability check, and `LogHandler::reexecute()` feeds that stored payload back through `Flow::execute()` inside the replaying administrator&amp;#39;s session without validating the identity that originally produced the data, causing `RegistrationController::updateUser()` to resolve the target user ID to the administrator and write the attacker-supplied password via `wp_update_user()`. This makes it possible for unauthenticated attackers to overwrite the administrator&amp;#39;s password and fully take over the administrator account. Exploitation requires that an administrator has configured a flow mapping a user-supplied form field to the `user_pass` parameter of the WP User Registration &amp;#34;Update User&amp;#34; action, and that the administrator subsequently clicks &amp;#34;Re-execute&amp;#34; on the failure log row produced by the anonymous submission from the plugin&amp;#39;s log screen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-104749</guid>
    </item>
  </channel>
</rss>
