<?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>Sun, 08 Nov 2026 07:23:05 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-33944</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-33944</link>
      <description>&lt;p&gt;Dolibarr is an open-source enterprise resource planning and customer relationship management application. Prior to 22.0.5 and 23.0.1, there is a SQL injection vulnerability in the Third Party company update functionality. The application concatenates the  localtax1_value  and  localtax2_value  properties into an SQL UPDATE statement without numeric conversion or other appropriate sanitization. An authenticated user with Third Party create or edit permission can submit crafted  lt1  or  lt2  POST parameters to read sensitive database information, including password hashes, API keys, and business data, or modify third-party records. This issue is fixed in versions 22.0.5 and 23.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Dolibarr is an open-source enterprise resource planning and customer relationship management application. Prior to 22.0.5 and 23.0.1, there is a SQL injection vulnerability in the Third Party company update functionality. The application concatenates the  localtax1_value  and  localtax2_value  properties into an SQL UPDATE statement without numeric conversion or other appropriate sanitization. An authenticated user with Third Party create or edit permission can submit crafted  lt1  or  lt2  POST parameters to read sensitive database information, including password hashes, API keys, and business data, or modify third-party records. This issue is fixed in versions 22.0.5 and 23.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-33944</guid>
    </item>
    <item>
      <title>GHSA-v5fq-cf5m-vwv7 — Dolibarr has SQL Injection in societe/class/societe.class.php via localtax1_value parameter</title>
      <link>https://db.gcve.eu/vuln/ghsa-v5fq-cf5m-vwv7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: dolibarr/dolibarr&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A SQL Injection vulnerability exists in the Third Party (Company) update functionality of Dolibarr ERP/CRM. The `localtax1_value` parameter (`lt1`) is concatenated
  directly into an SQL UPDATE statement in `societe/class/societe.class.php` at line 1672 without any escaping, type casting, or parameterized query binding.&lt;/p&gt;
&lt;p&gt;An authenticated user with standard &amp;#34;Third Party: Create/Edit&amp;#34; permission can extract any data from the database, including password hashes, API keys, and all
  business data.&lt;/p&gt;
&lt;p&gt;Tested on Dolibarr v23.0.0 (latest stable), default installation via official Docker image, MariaDB 10.11. No custom modules, no modified configuration.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Vulnerable code** (`societe/class/societe.class.php`, line 1672):
  ```php
  $sql .= &amp;#34;,localtax1_value =&amp;#34;.$this-&amp;gt;localtax1_value;
  ```&lt;/p&gt;
&lt;p&gt;The value comes from `GETPOST(&amp;#39;lt1&amp;#39;, &amp;#39;alpha&amp;#39;)` (`societe/card.php`, line 1135). The only sanitization applied is `trim()` at line 1528 — no `(float)` cast, no
  `$db-&amp;gt;escape()`.&lt;/p&gt;
&lt;p&gt;The `alpha` input filter strips HTML tags and double quotes but does **not** strip single quotes, parentheses, commas, or SQL keywords. Since the injection point is
   in a numeric SQL context (no quotes around the value), the attacker needs none of the filtered characters.&lt;/p&gt;
&lt;p&gt;**Why the WAF does not block this:** Dolibarr&amp;#39;s WAF (`waf.inc.php`) only checks SQL injection patterns in **GET** parameters, not POST. The POST-based `lt1`
  parameter bypasses it entirely.&lt;/p&gt;
&lt;p&gt;**The same vuln…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: dolibarr/dolibarr&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A SQL Injection vulnerability exists in the Third Party (Company) update functionality of Dolibarr ERP/CRM. The `localtax1_value` parameter (`lt1`) is concatenated
  directly into an SQL UPDATE statement in `societe/class/societe.class.php` at line 1672 without any escaping, type casting, or parameterized query binding.&lt;/p&gt;
&lt;p&gt;An authenticated user with standard &amp;#34;Third Party: Create/Edit&amp;#34; permission can extract any data from the database, including password hashes, API keys, and all
  business data.&lt;/p&gt;
&lt;p&gt;Tested on Dolibarr v23.0.0 (latest stable), default installation via official Docker image, MariaDB 10.11. No custom modules, no modified configuration.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Vulnerable code** (`societe/class/societe.class.php`, line 1672):
  ```php
  $sql .= &amp;#34;,localtax1_value =&amp;#34;.$this-&amp;gt;localtax1_value;
  ```&lt;/p&gt;
&lt;p&gt;The value comes from `GETPOST(&amp;#39;lt1&amp;#39;, &amp;#39;alpha&amp;#39;)` (`societe/card.php`, line 1135). The only sanitization applied is `trim()` at line 1528 — no `(float)` cast, no
  `$db-&amp;gt;escape()`.&lt;/p&gt;
&lt;p&gt;The `alpha` input filter strips HTML tags and double quotes but does **not** strip single quotes, parentheses, commas, or SQL keywords. Since the injection point is
   in a numeric SQL context (no quotes around the value), the attacker needs none of the filtered characters.&lt;/p&gt;
&lt;p&gt;**Why the WAF does not block this:** Dolibarr&amp;#39;s WAF (`waf.inc.php`) only checks SQL injection patterns in **GET** parameters, not POST. The POST-based `lt1`
  parameter bypasses it entirely.&lt;/p&gt;
&lt;p&gt;**The same vuln…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-v5fq-cf5m-vwv7</guid>
    </item>
  </channel>
</rss>
