https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 16:52:20 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-349643 EUVD-2026-349643 https://cve.radiocsirt.org/vuln/euvd-2026-349643 https://cve.radiocsirt.org/vuln/fkie_cve-2026-71247 <p>Documenso&#39;s sign-field-with-token.ts, used by the live document-signing UI, allows a recipient with the ASSISTANT role to fetch and complete fields belonging to any later-or-equal-order, not-yet-signed recipient in the same envelope, with no restriction on field type. A newer V2 signing path (sign-envelope-field.ts) explicitly blocks assistants from completing SIGNATURE fields, and the project&#39;s own test suite comments confirm this guard is absent from the V1 path used here.</p> <p>Documenso&#39;s sign-field-with-token.ts, used by the live document-signing UI, allows a recipient with the ASSISTANT role to fetch and complete fields belonging to any later-or-equal-order, not-yet-signed recipient in the same envelope, with no restriction on field type. A newer V2 signing path (sign-envelope-field.ts) explicitly blocks assistants from completing SIGNATURE fields, and the project&#39;s own test suite comments confirm this guard is absent from the V1 path used here.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-71247 https://cve.radiocsirt.org/vuln/ghsa-v65x-57rf-cpg3 <p>Documenso&#39;s sign-field-with-token.ts, used by the live document-signing UI, allows a recipient with the ASSISTANT role to fetch and complete fields belonging to any later-or-equal-order, not-yet-signed recipient in the same envelope, with no restriction on field type. The handler upserts a Signature record tied to the target field&#39;s recipientId with no check that field.type is SIGNATURE and the acting recipient owns it. A newer V2 signing path (sign-envelope-field.ts) explicitly blocks assistants from completing SIGNATURE fields, and the project&#39;s own test suite comments confirm this guard is absent from the V1 path used here. In a sequential-signing document, an assistant recipient can therefore forge another signer&#39;s signature field.</p> <p>Documenso&#39;s sign-field-with-token.ts, used by the live document-signing UI, allows a recipient with the ASSISTANT role to fetch and complete fields belonging to any later-or-equal-order, not-yet-signed recipient in the same envelope, with no restriction on field type. The handler upserts a Signature record tied to the target field&#39;s recipientId with no check that field.type is SIGNATURE and the acting recipient owns it. A newer V2 signing path (sign-envelope-field.ts) explicitly blocks assistants from completing SIGNATURE fields, and the project&#39;s own test suite comments confirm this guard is absent from the V1 path used here. In a sequential-signing document, an assistant recipient can therefore forge another signer&#39;s signature field.</p> https://cve.radiocsirt.org/vuln/ghsa-v65x-57rf-cpg3