<?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>Thu, 01 Oct 2026 16:41:41 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-61453</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-61453</link>
      <description>&lt;p&gt;Grav v2.0.0 contains a cross-site scripting vulnerability (fixed in 2.0.1). The XSS blueprint validator (Security::detectXss()) runs on raw page content before Twig processing. When Twig content processing is enabled (twig_content.process_enabled: true), an attacker with page-write API permission can use Twig&amp;#39;s string concatenation operator (~) to dynamically construct event handler names, dangerous tag names, or dangerous protocols at render time (e.g. {% set x = &amp;#34;on&amp;#34; ~ &amp;#34;error&amp;#34; %}). The validator sees only the harmless Twig expression and allows the content, but after Twig rendering the output (rendered via {{ page.content|raw }}) contains an active payload such as &amp;lt;img src=1 onerror=alert(1)&amp;gt;, executing arbitrary JavaScript in visitors&amp;#39; browsers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Grav v2.0.0 contains a cross-site scripting vulnerability (fixed in 2.0.1). The XSS blueprint validator (Security::detectXss()) runs on raw page content before Twig processing. When Twig content processing is enabled (twig_content.process_enabled: true), an attacker with page-write API permission can use Twig&amp;#39;s string concatenation operator (~) to dynamically construct event handler names, dangerous tag names, or dangerous protocols at render time (e.g. {% set x = &amp;#34;on&amp;#34; ~ &amp;#34;error&amp;#34; %}). The validator sees only the harmless Twig expression and allows the content, but after Twig rendering the output (rendered via {{ page.content|raw }}) contains an active payload such as &amp;lt;img src=1 onerror=alert(1)&amp;gt;, executing arbitrary JavaScript in visitors&amp;#39; browsers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-61453</guid>
    </item>
    <item>
      <title>GHSA-2c4f-86xc-cr74 — Grav: XSS Blueprint Validation Bypass via Twig String Concatenation</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-2c4f-86xc-cr74</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: getgrav/grav&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The XSS blueprint validator (`Security::detectXss()`) runs on the **raw page content before Twig processing**. An attacker can use Twig&amp;#39;s string concatenation operator (`~`) to dynamically construct an event handler name at render time. The validator sees `{{ &amp;#34;on&amp;#34; ~ &amp;#34;error&amp;#34; }}` - a harmless Twig expression - and allows the content. After Twig processes the template, the output contains `&amp;lt;img src=1 onerror=alert(1)&amp;gt;` which is rendered via `{{ content|raw }}` and executes in the victim&amp;#39;s browser.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;**The two-stage attack** exploits the separation between validation and rendering:&lt;/p&gt;
&lt;p&gt;**Stage 1 - what the XSS validator sees** (raw page content):&lt;/p&gt;
&lt;p&gt;```twig
{% set x = &amp;#34;on&amp;#34; ~ &amp;#34;error&amp;#34; %}
&amp;lt;img src=1 {{ x }}=alert(document.domain)&amp;gt;
```&lt;/p&gt;
&lt;p&gt;The `detectXss()` function scans this string. The `on_events` regex looks for `&amp;lt;[^&amp;gt;]*?[\s\x00-\x20\&amp;#34;\&amp;#39;\/](on\s*[a-z]+|xmlns)\s*=` inside HTML tags. In `{{ x }}`, the `{` character is not in the boundary set `[\s\x00-\x20\&amp;#34;\&amp;#39;\/]`, and `x` is not `on`. **No match - passes validation.**&lt;/p&gt;
&lt;p&gt;**Stage 2 - what Twig produces** (after rendering):&lt;/p&gt;
&lt;p&gt;```html
&amp;lt;img src=1 onerror=alert(document.domain)&amp;gt;
```&lt;/p&gt;
&lt;p&gt;The validator never re-inspects Twig output. The theme template renders this via `{{ page.content|raw }}` (confirmed in `quark2/templates/default.html.twig:5`), so no auto-escaping occurs.&lt;/p&gt;
&lt;p&gt;**Why `{% set %}` and `~` are allowed** - `system/config/security.yaml:125-145`:&lt;/p&gt;
&lt;p&gt;```yaml
allowed_tags:
  - set          # ← allows variable assignment…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: getgrav/grav&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The XSS blueprint validator (`Security::detectXss()`) runs on the **raw page content before Twig processing**. An attacker can use Twig&amp;#39;s string concatenation operator (`~`) to dynamically construct an event handler name at render time. The validator sees `{{ &amp;#34;on&amp;#34; ~ &amp;#34;error&amp;#34; }}` - a harmless Twig expression - and allows the content. After Twig processes the template, the output contains `&amp;lt;img src=1 onerror=alert(1)&amp;gt;` which is rendered via `{{ content|raw }}` and executes in the victim&amp;#39;s browser.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;**The two-stage attack** exploits the separation between validation and rendering:&lt;/p&gt;
&lt;p&gt;**Stage 1 - what the XSS validator sees** (raw page content):&lt;/p&gt;
&lt;p&gt;```twig
{% set x = &amp;#34;on&amp;#34; ~ &amp;#34;error&amp;#34; %}
&amp;lt;img src=1 {{ x }}=alert(document.domain)&amp;gt;
```&lt;/p&gt;
&lt;p&gt;The `detectXss()` function scans this string. The `on_events` regex looks for `&amp;lt;[^&amp;gt;]*?[\s\x00-\x20\&amp;#34;\&amp;#39;\/](on\s*[a-z]+|xmlns)\s*=` inside HTML tags. In `{{ x }}`, the `{` character is not in the boundary set `[\s\x00-\x20\&amp;#34;\&amp;#39;\/]`, and `x` is not `on`. **No match - passes validation.**&lt;/p&gt;
&lt;p&gt;**Stage 2 - what Twig produces** (after rendering):&lt;/p&gt;
&lt;p&gt;```html
&amp;lt;img src=1 onerror=alert(document.domain)&amp;gt;
```&lt;/p&gt;
&lt;p&gt;The validator never re-inspects Twig output. The theme template renders this via `{{ page.content|raw }}` (confirmed in `quark2/templates/default.html.twig:5`), so no auto-escaping occurs.&lt;/p&gt;
&lt;p&gt;**Why `{% set %}` and `~` are allowed** - `system/config/security.yaml:125-145`:&lt;/p&gt;
&lt;p&gt;```yaml
allowed_tags:
  - set          # ← allows variable assignment…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-2c4f-86xc-cr74</guid>
    </item>
  </channel>
</rss>
