<?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, 23 Oct 2026 23:21:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2019-16763 — XSS in Pannellum from 2.5.0 through 2.5.4</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2019-16763</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; mpretroff pannellum&lt;/p&gt;
&lt;p&gt;In Pannellum from 2.5.0 through 2.5.4 URLs were not sanitized for data URIs (or vbscript:), allowing for potential XSS attacks. Such an attack would require a user to click on a hot spot to execute and would require an attacker-provided configuration. The most plausible potential attack would be if pannellum.htm was hosted on a domain that shared cookies with the targeted site&amp;#39;s user authentication; an &amp;amp;lt;iframe&amp;amp;gt; could then be embedded on the attacker&amp;#39;s site using pannellum.htm from the targeted site, which would allow the attacker to potentially access information from the targeted site as the authenticated user (or worse if the targeted site did not have adequate CSRF protections) if the user clicked on a hot spot in the attacker&amp;#39;s embedded panorama viewer. This was patched in version 2.5.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; mpretroff pannellum&lt;/p&gt;
&lt;p&gt;In Pannellum from 2.5.0 through 2.5.4 URLs were not sanitized for data URIs (or vbscript:), allowing for potential XSS attacks. Such an attack would require a user to click on a hot spot to execute and would require an attacker-provided configuration. The most plausible potential attack would be if pannellum.htm was hosted on a domain that shared cookies with the targeted site&amp;#39;s user authentication; an &amp;amp;lt;iframe&amp;amp;gt; could then be embedded on the attacker&amp;#39;s site using pannellum.htm from the targeted site, which would allow the attacker to potentially access information from the targeted site as the authenticated user (or worse if the targeted site did not have adequate CSRF protections) if the user clicked on a hot spot in the attacker&amp;#39;s embedded panorama viewer. This was patched in version 2.5.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2019-16763</guid>
    </item>
  </channel>
</rss>
