<?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://vulnerability.circl.lu</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, 05 Oct 2026 12:13:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-85600 — Grav Admin before 2.0.21 Stored XSS via username</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-85600</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; getgrav grav-plugin-admin2&lt;/p&gt;
&lt;p&gt;Grav Admin (getgrav/grav-plugin-admin2) versions &amp;lt;= 2.0.19 contain a stored cross-site scripting vulnerability in the tHtml() function (src/lib/stores/i18n.svelte.ts), which substitutes untrusted parameters such as usernames into translation templates before parsing the result as markdown. Grav&amp;#39;s server-side username validation (DataUser::isValidUsername) blocks filesystem-dangerous characters but not &amp;lt;, &amp;gt;, &amp;#34;, or &amp;#39;, allowing an attacker to register a username containing an HTML payload. When an administrator views a UI surface that renders the username through tHtml()—such as the two-factor force-disable confirmation prompt or the &amp;#39;page is locked&amp;#39; editor notice—the payload executes in their authenticated session. Fixed in 2.0.21.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; getgrav grav-plugin-admin2&lt;/p&gt;
&lt;p&gt;Grav Admin (getgrav/grav-plugin-admin2) versions &amp;lt;= 2.0.19 contain a stored cross-site scripting vulnerability in the tHtml() function (src/lib/stores/i18n.svelte.ts), which substitutes untrusted parameters such as usernames into translation templates before parsing the result as markdown. Grav&amp;#39;s server-side username validation (DataUser::isValidUsername) blocks filesystem-dangerous characters but not &amp;lt;, &amp;gt;, &amp;#34;, or &amp;#39;, allowing an attacker to register a username containing an HTML payload. When an administrator views a UI surface that renders the username through tHtml()—such as the two-factor force-disable confirmation prompt or the &amp;#39;page is locked&amp;#39; editor notice—the payload executes in their authenticated session. Fixed in 2.0.21.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-85600</guid>
    </item>
  </channel>
</rss>
