<?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://cve.radiocsirt.org</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>Fri, 09 Oct 2026 04:11:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-19872 — HTML::FormHandler versions before 0.410000 for Perl allow cross-site scripting via a submitted value rendered unescaped…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-19872</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HTML-FormHandler&lt;/p&gt;
&lt;p&gt;HTML::FormHandler versions before 0.410000 for Perl allow cross-site scripting via a submitted value rendered unescaped in an error message.&lt;/p&gt;
&lt;p&gt;The wrappers and renderers that emit a form&amp;#39;s errors interpolate the error string straight into HTML with no escaping. Two of the library&amp;#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.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s own escaping template layer rather than the library&amp;#39;s rendering roles are not affected.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s origin. Re-rendering a rejected value later gives the stored variant.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HTML-FormHandler&lt;/p&gt;
&lt;p&gt;HTML::FormHandler versions before 0.410000 for Perl allow cross-site scripting via a submitted value rendered unescaped in an error message.&lt;/p&gt;
&lt;p&gt;The wrappers and renderers that emit a form&amp;#39;s errors interpolate the error string straight into HTML with no escaping. Two of the library&amp;#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.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s own escaping template layer rather than the library&amp;#39;s rendering roles are not affected.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s origin. Re-rendering a rejected value later gives the stored variant.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-19872</guid>
    </item>
  </channel>
</rss>
