<?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>Mon, 28 Sep 2026 11:41:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-73374 — Stored Cross-Site Scripting (XSS) via Unescaped CNA Reference Tags in vulnerability-lookup</title>
      <link>https://db.gcve.eu/vuln/cve-2026-73374</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vulnerability-lookup&lt;/p&gt;
&lt;p&gt;A stored cross-site scripting (XSS) vulnerability existed in Vulnerability-Lookup in the render_tag_badges Jinja filter used to display reference tags associated with vulnerability records.&lt;/p&gt;
&lt;p&gt;Values from containers.cna.references[].tags[] were directly interpolated into HTML badge elements and the resulting string was wrapped in markupsafe.Markup. Because Markup marks the generated content as safe, Jinja&amp;#39;s automatic HTML escaping was bypassed.&lt;/p&gt;
&lt;p&gt;An authenticated user with permissions to create or modify vulnerability records, such as a user holding the vulnerability:create or vulnerability:modify permission, could submit a crafted reference tag through the CNA API containing arbitrary HTML or JavaScript-capable markup.&lt;/p&gt;
&lt;p&gt;The malicious value would subsequently be stored as part of the vulnerability record. When another user visited the corresponding public /cve/&amp;lt;id&amp;gt; or /vuln/&amp;lt;id&amp;gt; page, the crafted tag would be rendered as HTML in the viewer&amp;#39;s browser. This could result in JavaScript execution in the security context of the Vulnerability-Lookup application.&lt;/p&gt;
&lt;p&gt;Successful exploitation could allow an attacker to perform actions in the context of a victim, access information available to the victim&amp;#39;s browser session, or modify page content. As the affected vulnerability pages can be accessed publicly, exploitation may affect users who are not authenticated.&lt;/p&gt;
&lt;p&gt;The issue was corrected by applying markupsafe.escape() to each reference tag before inserting it into the HTML badge markup, wh…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; vulnerability-lookup&lt;/p&gt;
&lt;p&gt;A stored cross-site scripting (XSS) vulnerability existed in Vulnerability-Lookup in the render_tag_badges Jinja filter used to display reference tags associated with vulnerability records.&lt;/p&gt;
&lt;p&gt;Values from containers.cna.references[].tags[] were directly interpolated into HTML badge elements and the resulting string was wrapped in markupsafe.Markup. Because Markup marks the generated content as safe, Jinja&amp;#39;s automatic HTML escaping was bypassed.&lt;/p&gt;
&lt;p&gt;An authenticated user with permissions to create or modify vulnerability records, such as a user holding the vulnerability:create or vulnerability:modify permission, could submit a crafted reference tag through the CNA API containing arbitrary HTML or JavaScript-capable markup.&lt;/p&gt;
&lt;p&gt;The malicious value would subsequently be stored as part of the vulnerability record. When another user visited the corresponding public /cve/&amp;lt;id&amp;gt; or /vuln/&amp;lt;id&amp;gt; page, the crafted tag would be rendered as HTML in the viewer&amp;#39;s browser. This could result in JavaScript execution in the security context of the Vulnerability-Lookup application.&lt;/p&gt;
&lt;p&gt;Successful exploitation could allow an attacker to perform actions in the context of a victim, access information available to the victim&amp;#39;s browser session, or modify page content. As the affected vulnerability pages can be accessed publicly, exploitation may affect users who are not authenticated.&lt;/p&gt;
&lt;p&gt;The issue was corrected by applying markupsafe.escape() to each reference tag before inserting it into the HTML badge markup, wh…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-73374</guid>
    </item>
  </channel>
</rss>
