<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-09T09:23:14.387182+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-270455</id>
    <title>EUVD-2026-270455</title>
    <updated>2026-10-09T09:23:14.390201+00:00</updated>
    <content>EUVD-2026-270455</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-270455"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27469</id>
    <title>fkie_cve-2026-27469</title>
    <updated>2026-10-09T09:23:14.390264+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-27469"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9fww-8cpr-q66r</id>
    <title>GHSA-9fww-8cpr-q66r — Isso affected by Stored XSS via comment website field</title>
    <updated>2026-10-09T09:23:14.390301+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: isso</p>
<p>## Impact</p>
<p>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).</p>
<p>The same escaping was missing entirely from the user-facing comment edit endpoint (PUT /id/&lt;id&gt;) and the moderation edit endpoint (POST /id/&lt;id&gt;/edit/&lt;key&gt;).</p>
<p>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.</p>
<p>## Patches</p>
<p>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/&lt;id&gt;, POST /id/&lt;id&gt;/edit/&lt;key&gt;), and adds input validation and escaping to the moderation edit endpoint which previously had neither.</p>
<p>## Workarounds</p>
<p>Enabling comment moderation (moderati…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9fww-8cpr-q66r"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-2527</id>
    <title>PYSEC-2026-2527 — Isso affected by Stored XSS via comment website field</title>
    <updated>2026-10-09T09:23:14.390348+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: isso</p>
<p>## Impact</p>
<p>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).</p>
<p>The same escaping was missing entirely from the user-facing comment edit endpoint (PUT /id/&lt;id&gt;) and the moderation edit endpoint (POST /id/&lt;id&gt;/edit/&lt;key&gt;).</p>
<p>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.</p>
<p>## Patches</p>
<p>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/&lt;id&gt;, POST /id/&lt;id&gt;/edit/&lt;key&gt;), and adds input validation and escaping to the moderation edit endpoint which previously had neither.</p>
<p>## Workarounds</p>
<p>Enabling comment moderation (moderati…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-2527"/>
  </entry>
</feed>
