<?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>Sun, 04 Oct 2026 11:34:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-81729 — Dolibarr before 23.0.4 Incorrect Authorization on REST API Document Deletion</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-81729</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dolibarr&lt;/p&gt;
&lt;p&gt;Dolibarr before 23.0.4 authorizes REST API document deletion against the wrong permission. Documents::delete() in htdocs/api/class/api_documents.class.php calls dol_check_secure_access_document() with the mode argument &amp;#39;read&amp;#39; when handling DELETE /api/index.php/documents, while the sibling builddoc() path passes &amp;#39;write&amp;#39;, the correct mode for an operation that modifies stored data. An authenticated API user who holds only a read permission for a document-bearing module, for example societe:lire or facture:lire, and no create, write, delete or admin permission, therefore passes the check and can permanently delete that module&amp;#39;s documents: third-party files, invoices, orders, proposals, project files and generated PDFs, with no recovery path. The call site is htdocs/api/class/api_documents.class.php:1276 in 23.0.3 and passes &amp;#39;write&amp;#39; from 23.0.4 onward.&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 23.0.4 authorizes REST API document deletion against the wrong permission. Documents::delete() in htdocs/api/class/api_documents.class.php calls dol_check_secure_access_document() with the mode argument &amp;#39;read&amp;#39; when handling DELETE /api/index.php/documents, while the sibling builddoc() path passes &amp;#39;write&amp;#39;, the correct mode for an operation that modifies stored data. An authenticated API user who holds only a read permission for a document-bearing module, for example societe:lire or facture:lire, and no create, write, delete or admin permission, therefore passes the check and can permanently delete that module&amp;#39;s documents: third-party files, invoices, orders, proposals, project files and generated PDFs, with no recovery path. The call site is htdocs/api/class/api_documents.class.php:1276 in 23.0.3 and passes &amp;#39;write&amp;#39; from 23.0.4 onward.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-81729</guid>
    </item>
  </channel>
</rss>
