<?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://vulnerability.circl.lu</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 21:25:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-81728 — Dolibarr before 24.0.0 SQL Injection via the CSV and XLSX Import Update Keys</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-81728</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dolibarr&lt;/p&gt;
&lt;p&gt;Dolibarr before 24.0.0 contains a SQL injection in its CSV and XLSX import wizard. The wizard reads its update keys with GETPOST(&amp;#39;updatekeys&amp;#39;, &amp;#39;array&amp;#39;) in htdocs/imports/import.php, which applies only the generic alphanohtml filter: that strips HTML but leaves SQL keywords, comment markers, parentheses, spaces and quotes intact. import_insert() in htdocs/core/modules/import/import_csv.modules.php then iterates the submitted values and builds a filter with $where[] = $key.&amp;#39; = &amp;#39;.$data[$key], having first applied preg_replace(&amp;#39;/^.*\./i&amp;#39;, &amp;#39;&amp;#39;, $key), an alias strip that does nothing to a value containing no dot. The assembled string is executed through $this-&amp;gt;db-&amp;gt;query(). The injected SELECT resolves the row id that the import then assigns to $lastinsertid, which becomes the WHERE target of a subsequent UPDATE, so a UNION SELECT returning an attacker-chosen integer both exfiltrates arbitrary table content and redirects which row the import overwrites; for category link tables the raw filter array is spliced into that UPDATE directly. The interface offers a fixed list of legitimate column codes but the server never checks the submitted values against it. A user holding the import permission can exploit this. Release 23.0.4 does not carry the fix; the allow-list test was added in 24.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dolibarr&lt;/p&gt;
&lt;p&gt;Dolibarr before 24.0.0 contains a SQL injection in its CSV and XLSX import wizard. The wizard reads its update keys with GETPOST(&amp;#39;updatekeys&amp;#39;, &amp;#39;array&amp;#39;) in htdocs/imports/import.php, which applies only the generic alphanohtml filter: that strips HTML but leaves SQL keywords, comment markers, parentheses, spaces and quotes intact. import_insert() in htdocs/core/modules/import/import_csv.modules.php then iterates the submitted values and builds a filter with $where[] = $key.&amp;#39; = &amp;#39;.$data[$key], having first applied preg_replace(&amp;#39;/^.*\./i&amp;#39;, &amp;#39;&amp;#39;, $key), an alias strip that does nothing to a value containing no dot. The assembled string is executed through $this-&amp;gt;db-&amp;gt;query(). The injected SELECT resolves the row id that the import then assigns to $lastinsertid, which becomes the WHERE target of a subsequent UPDATE, so a UNION SELECT returning an attacker-chosen integer both exfiltrates arbitrary table content and redirects which row the import overwrites; for category link tables the raw filter array is spliced into that UPDATE directly. The interface offers a fixed list of legitimate column codes but the server never checks the submitted values against it. A user holding the import permission can exploit this. Release 23.0.4 does not carry the fix; the allow-list test was added in 24.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-81728</guid>
    </item>
  </channel>
</rss>
