https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 04:34:39 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-19872 <p>HTML::FormHandler versions before 0.410000 for Perl allow cross-site scripting via a submitted value rendered unescaped in an error message.</p> <p>The wrappers and renderers that emit a form&#39;s errors interpolate the error string straight into HTML with no escaping. Two of the library&#39;s own messages, no_match and not_allowed, splice the submitted value into that string, and a failing type constraint puts the rejected value into the message it builds, which _apply_actions hands to add_error.</p> <p>A field declared with a check regexp, a check list or a type constraint reaches those messages, with no custom validator and no non-default configuration. Errors rendered through an application&#39;s own escaping template layer rather than the library&#39;s rendering roles are not affected.</p> <p>A request over the network that submits markup to such a field gets it back live inside the error span, running script in the victim&#39;s origin. Re-rendering a rejected value later gives the stored variant.</p> <p>HTML::FormHandler versions before 0.410000 for Perl allow cross-site scripting via a submitted value rendered unescaped in an error message.</p> <p>The wrappers and renderers that emit a form&#39;s errors interpolate the error string straight into HTML with no escaping. Two of the library&#39;s own messages, no_match and not_allowed, splice the submitted value into that string, and a failing type constraint puts the rejected value into the message it builds, which _apply_actions hands to add_error.</p> <p>A field declared with a check regexp, a check list or a type constraint reaches those messages, with no custom validator and no non-default configuration. Errors rendered through an application&#39;s own escaping template layer rather than the library&#39;s rendering roles are not affected.</p> <p>A request over the network that submits markup to such a field gets it back live inside the error span, running script in the victim&#39;s origin. Re-rendering a rejected value later gives the stored variant.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-19872 https://vulnerability.circl.lu/vuln/ghsa-74pj-vp7j-2f6m <p>HTML::FormHandler versions before 0.410000 for Perl allow cross-site scripting via a submitted value rendered unescaped in an error message.</p> <p>The wrappers and renderers that emit a form&#39;s errors interpolate the error string straight into HTML with no escaping. Two of the library&#39;s own messages, no_match and not_allowed, splice the submitted value into that string, and a failing type constraint puts the rejected value into the message it builds, which _apply_actions hands to add_error.</p> <p>A field declared with a check regexp, a check list or a type constraint reaches those messages, with no custom validator and no non-default configuration. Errors rendered through an application&#39;s own escaping template layer rather than the library&#39;s rendering roles are not affected.</p> <p>A request over the network that submits markup to such a field gets it back live inside the error span, running script in the victim&#39;s origin. Re-rendering a rejected value later gives the stored variant.</p> <p>HTML::FormHandler versions before 0.410000 for Perl allow cross-site scripting via a submitted value rendered unescaped in an error message.</p> <p>The wrappers and renderers that emit a form&#39;s errors interpolate the error string straight into HTML with no escaping. Two of the library&#39;s own messages, no_match and not_allowed, splice the submitted value into that string, and a failing type constraint puts the rejected value into the message it builds, which _apply_actions hands to add_error.</p> <p>A field declared with a check regexp, a check list or a type constraint reaches those messages, with no custom validator and no non-default configuration. Errors rendered through an application&#39;s own escaping template layer rather than the library&#39;s rendering roles are not affected.</p> <p>A request over the network that submits markup to such a field gets it back live inside the error span, running script in the victim&#39;s origin. Re-rendering a rejected value later gives the stored variant.</p> https://vulnerability.circl.lu/vuln/ghsa-74pj-vp7j-2f6m https://vulnerability.circl.lu/vuln/opensuse-su-2026:11745-1 <p>perl-HTML-FormHandler-0.410.2-1.1 on GA media</p> <p>perl-HTML-FormHandler-0.410.2-1.1 on GA media</p> https://vulnerability.circl.lu/vuln/opensuse-su-2026:11745-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-19872 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: libhtml-formhandler-perl, Ubuntu:18.04:LTS: libhtml-formhandler-perl, Ubuntu:20.04:LTS: libhtml-formhandler-perl, Ubuntu:22.04:LTS: libhtml-formhandler-perl, Ubuntu:24.04:LTS: libhtml-formhandler-perl, Ubuntu:26.04:LTS: libhtml-formhandler-perl</p> <p>HTML::FormHandler versions before 0.410000 for Perl allow cross-site scripting via a submitted value rendered unescaped in an error message. The wrappers and renderers that emit a form&#39;s errors interpolate the error string straight into HTML with no escaping. Two of the library&#39;s own messages, no_match and not_allowed, splice the submitted value into that string, and a failing type constraint puts the rejected value into the message it builds, which _apply_actions hands to add_error. A field declared with a check regexp, a check list or a type constraint reaches those messages, with no custom validator and no non-default configuration. Errors rendered through an application&#39;s own escaping template layer rather than the library&#39;s rendering roles are not affected. A request over the network that submits markup to such a field gets it back live inside the error span, running script in the victim&#39;s origin. Re-rendering a rejected value later gives the stored variant.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: libhtml-formhandler-perl, Ubuntu:18.04:LTS: libhtml-formhandler-perl, Ubuntu:20.04:LTS: libhtml-formhandler-perl, Ubuntu:22.04:LTS: libhtml-formhandler-perl, Ubuntu:24.04:LTS: libhtml-formhandler-perl, Ubuntu:26.04:LTS: libhtml-formhandler-perl</p> <p>HTML::FormHandler versions before 0.410000 for Perl allow cross-site scripting via a submitted value rendered unescaped in an error message. The wrappers and renderers that emit a form&#39;s errors interpolate the error string straight into HTML with no escaping. Two of the library&#39;s own messages, no_match and not_allowed, splice the submitted value into that string, and a failing type constraint puts the rejected value into the message it builds, which _apply_actions hands to add_error. A field declared with a check regexp, a check list or a type constraint reaches those messages, with no custom validator and no non-default configuration. Errors rendered through an application&#39;s own escaping template layer rather than the library&#39;s rendering roles are not affected. A request over the network that submits markup to such a field gets it back live inside the error span, running script in the victim&#39;s origin. Re-rendering a rejected value later gives the stored variant.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-19872