<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>XSS on GMO Flatt Security Research</title>
    <link>https://flatt.tech/research/tags/xss/</link>
    <description>Recent content in XSS on GMO Flatt Security Research</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 08 Jul 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://flatt.tech/research/tags/xss/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why XSS Persists in This Frameworks Era?</title>
      <link>https://flatt.tech/research/posts/why-xss-persists-in-this-frameworks-era/</link>
      <pubDate>Tue, 08 Jul 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/why-xss-persists-in-this-frameworks-era/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hi, I&amp;rsquo;m canalun (&lt;a href=&#34;https://x.com/i_am_canalun&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@i_am_canalun&lt;/a&gt;&#xA;), a security researcher at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;This article explores the question: &amp;ldquo;Why Does XSS Still Occur So Frequently?&amp;rdquo; We will delve into why this notorious and classic vulnerability despite the widespread adoption of built-in XSS countermeasures in modern development frameworks.&lt;/p&gt;&#xA;&lt;p&gt;The world of web development, especially frameworks, is evolving at a rapid pace, bringing improvements not only in development efficiency but also in security.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bypassing DOMPurify with good old XML</title>
      <link>https://flatt.tech/research/posts/bypassing-dompurify-with-good-old-xml/</link>
      <pubDate>Mon, 01 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/bypassing-dompurify-with-good-old-xml/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m RyotaK ( &lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA; ), a security engineer at Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;Recently, &lt;a href=&#34;https://twitter.com/slonser_&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@slonser_&lt;/a&gt;&#xA; found &lt;a href=&#34;https://blog.slonser.info/posts/dompurify-node-type-confusion/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;a bypass&lt;/a&gt;&#xA; in the DOMPurify when it&amp;rsquo;s used to sanitize XML documents.&#xA;After taking a look at the patch, I found two more bypasses of XML/HTML confusion, so I&amp;rsquo;m documenting it here.&lt;/p&gt;&#xA;&lt;h2 id=&#34;html--xml&#34;&gt;HTML != XML&lt;/h2&gt;&#xA;&lt;p&gt;As &lt;a href=&#34;https://twitter.com/slonser_&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@slonser_&lt;/a&gt;&#xA; wrote in his post, HTML and XML have a bit different parsing rules.&lt;br&gt;&#xA;For example, the following text is parsed as a single node in the XML parser, but the HTML parser recognizes the &lt;code&gt;h1&lt;/code&gt; tag.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
