<?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 08:40:45 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-270455</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-270455</link>
      <description>EUVD-2026-270455</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-270455</guid>
    </item>
    <item>
      <title>fkie_cve-2026-27469</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27469</link>
      <description>&lt;p&gt;Isso is a lightweight commenting server written in Python and JavaScript. In commits before 0afbfe0691ee237963e8fb0b2ee01c9e55ca2144, there is a stored Cross-Site Scripting (XSS) vulnerability affecting the website and author comment fields. The website field was HTML-escaped using quote=False, which left single and double quotes unescaped. Since the frontend inserts the website value directly into a single-quoted href attribute via string concatenation, a single quote in the URL breaks out of the attribute context, allowing injection of arbitrary event handlers (e.g. onmouseover, onclick). The same escaping is missing entirely from the user-facing comment edit endpoint (PUT /id/) and the moderation edit endpoint (POST /id//edit/). This issue has been patched in commit 0afbfe0691ee237963e8fb0b2ee01c9e55ca2144. To workaround, nabling comment moderation (moderation = enabled = true in isso.cfg) prevents unauthenticated users from publishing comments, raising the bar for exploitation, but it does not fully mitigate the issue since a moderator activating a malicious comment would still expose visitors.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Isso is a lightweight commenting server written in Python and JavaScript. In commits before 0afbfe0691ee237963e8fb0b2ee01c9e55ca2144, there is a stored Cross-Site Scripting (XSS) vulnerability affecting the website and author comment fields. The website field was HTML-escaped using quote=False, which left single and double quotes unescaped. Since the frontend inserts the website value directly into a single-quoted href attribute via string concatenation, a single quote in the URL breaks out of the attribute context, allowing injection of arbitrary event handlers (e.g. onmouseover, onclick). The same escaping is missing entirely from the user-facing comment edit endpoint (PUT /id/) and the moderation edit endpoint (POST /id//edit/). This issue has been patched in commit 0afbfe0691ee237963e8fb0b2ee01c9e55ca2144. To workaround, nabling comment moderation (moderation = enabled = true in isso.cfg) prevents unauthenticated users from publishing comments, raising the bar for exploitation, but it does not fully mitigate the issue since a moderator activating a malicious comment would still expose visitors.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-27469</guid>
    </item>
    <item>
      <title>GHSA-9fww-8cpr-q66r — Isso affected by Stored XSS via comment website field</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9fww-8cpr-q66r</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: isso&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;This is a stored Cross-Site Scripting (XSS) vulnerability affecting the website and author comment fields. The website field was HTML-escaped using quote=False, which left single and double quotes unescaped. Since the frontend inserts the website value directly into a single-quoted href attribute via string concatenation, a single quote in the URL breaks out of the attribute context, allowing injection of arbitrary event handlers (e.g. onmouseover, onclick).&lt;/p&gt;
&lt;p&gt;The same escaping was missing entirely from the user-facing comment edit endpoint (PUT /id/&amp;lt;id&amp;gt;) and the moderation edit endpoint (POST /id/&amp;lt;id&amp;gt;/edit/&amp;lt;key&amp;gt;).&lt;/p&gt;
&lt;p&gt;Any visitor to a page embedding isso comments is impacted. No authentication or interaction beyond mouse movement is required to trigger a payload — an attacker can post a comment anonymously (moderation is off by default) with a crafted website URL, and the payload persists in the database and fires on every page load. With the full-page invisible overlay technique described in the report, the victim only needs to move their mouse.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in commit 3cf27c2. Users should upgrade to a version containing that commit once released. The fix applies html.escape(..., quote=True) to the website field across all three write paths (POST /new, PUT /id/&amp;lt;id&amp;gt;, POST /id/&amp;lt;id&amp;gt;/edit/&amp;lt;key&amp;gt;), and adds input validation and escaping to the moderation edit endpoint which previously had neither.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Enabling comment moderation (moderati…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: isso&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;This is a stored Cross-Site Scripting (XSS) vulnerability affecting the website and author comment fields. The website field was HTML-escaped using quote=False, which left single and double quotes unescaped. Since the frontend inserts the website value directly into a single-quoted href attribute via string concatenation, a single quote in the URL breaks out of the attribute context, allowing injection of arbitrary event handlers (e.g. onmouseover, onclick).&lt;/p&gt;
&lt;p&gt;The same escaping was missing entirely from the user-facing comment edit endpoint (PUT /id/&amp;lt;id&amp;gt;) and the moderation edit endpoint (POST /id/&amp;lt;id&amp;gt;/edit/&amp;lt;key&amp;gt;).&lt;/p&gt;
&lt;p&gt;Any visitor to a page embedding isso comments is impacted. No authentication or interaction beyond mouse movement is required to trigger a payload — an attacker can post a comment anonymously (moderation is off by default) with a crafted website URL, and the payload persists in the database and fires on every page load. With the full-page invisible overlay technique described in the report, the victim only needs to move their mouse.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in commit 3cf27c2. Users should upgrade to a version containing that commit once released. The fix applies html.escape(..., quote=True) to the website field across all three write paths (POST /new, PUT /id/&amp;lt;id&amp;gt;, POST /id/&amp;lt;id&amp;gt;/edit/&amp;lt;key&amp;gt;), and adds input validation and escaping to the moderation edit endpoint which previously had neither.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Enabling comment moderation (moderati…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9fww-8cpr-q66r</guid>
    </item>
    <item>
      <title>PYSEC-2026-2527 — Isso affected by Stored XSS via comment website field</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2527</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: isso&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;This is a stored Cross-Site Scripting (XSS) vulnerability affecting the website and author comment fields. The website field was HTML-escaped using quote=False, which left single and double quotes unescaped. Since the frontend inserts the website value directly into a single-quoted href attribute via string concatenation, a single quote in the URL breaks out of the attribute context, allowing injection of arbitrary event handlers (e.g. onmouseover, onclick).&lt;/p&gt;
&lt;p&gt;The same escaping was missing entirely from the user-facing comment edit endpoint (PUT /id/&amp;lt;id&amp;gt;) and the moderation edit endpoint (POST /id/&amp;lt;id&amp;gt;/edit/&amp;lt;key&amp;gt;).&lt;/p&gt;
&lt;p&gt;Any visitor to a page embedding isso comments is impacted. No authentication or interaction beyond mouse movement is required to trigger a payload — an attacker can post a comment anonymously (moderation is off by default) with a crafted website URL, and the payload persists in the database and fires on every page load. With the full-page invisible overlay technique described in the report, the victim only needs to move their mouse.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in commit 3cf27c2. Users should upgrade to a version containing that commit once released. The fix applies html.escape(..., quote=True) to the website field across all three write paths (POST /new, PUT /id/&amp;lt;id&amp;gt;, POST /id/&amp;lt;id&amp;gt;/edit/&amp;lt;key&amp;gt;), and adds input validation and escaping to the moderation edit endpoint which previously had neither.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Enabling comment moderation (moderati…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: isso&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;This is a stored Cross-Site Scripting (XSS) vulnerability affecting the website and author comment fields. The website field was HTML-escaped using quote=False, which left single and double quotes unescaped. Since the frontend inserts the website value directly into a single-quoted href attribute via string concatenation, a single quote in the URL breaks out of the attribute context, allowing injection of arbitrary event handlers (e.g. onmouseover, onclick).&lt;/p&gt;
&lt;p&gt;The same escaping was missing entirely from the user-facing comment edit endpoint (PUT /id/&amp;lt;id&amp;gt;) and the moderation edit endpoint (POST /id/&amp;lt;id&amp;gt;/edit/&amp;lt;key&amp;gt;).&lt;/p&gt;
&lt;p&gt;Any visitor to a page embedding isso comments is impacted. No authentication or interaction beyond mouse movement is required to trigger a payload — an attacker can post a comment anonymously (moderation is off by default) with a crafted website URL, and the payload persists in the database and fires on every page load. With the full-page invisible overlay technique described in the report, the victim only needs to move their mouse.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in commit 3cf27c2. Users should upgrade to a version containing that commit once released. The fix applies html.escape(..., quote=True) to the website field across all three write paths (POST /new, PUT /id/&amp;lt;id&amp;gt;, POST /id/&amp;lt;id&amp;gt;/edit/&amp;lt;key&amp;gt;), and adds input validation and escaping to the moderation edit endpoint which previously had neither.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Enabling comment moderation (moderati…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2527</guid>
    </item>
  </channel>
</rss>
