<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ReCAPTCHA on antoniusblock</title>
    <link>https://blog.antoniusblock.net/tags/recaptcha/</link>
    <description>Recent content in ReCAPTCHA on antoniusblock</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>luca.p.fama@gmail.com (antoniusblock)</managingEditor>
    <webMaster>luca.p.fama@gmail.com (antoniusblock)</webMaster>
    <copyright>© 2026 antoniusblock</copyright>
    <lastBuildDate>Thu, 19 Mar 2026 16:43:00 +0100</lastBuildDate><atom:link href="https://blog.antoniusblock.net/tags/recaptcha/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>From Self-XSS to PII leakage via WAF bypass, CSRF login and window.opener abuse</title>
      <link>https://blog.antoniusblock.net/posts/self-xss-csrf-login/</link>
      <pubDate>Thu, 19 Mar 2026 16:43:00 +0100</pubDate>
      <author>luca.p.fama@gmail.com (antoniusblock)</author>
      <guid>https://blog.antoniusblock.net/posts/self-xss-csrf-login/</guid>
      <description>Turning a &amp;lsquo;0-impact&amp;rsquo; self-XSS into a real bug: how chaining it with CSRF and browser behaviors can lead to significant impact and data leakage.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://blog.antoniusblock.net/posts/self-xss-csrf-login/featured.png" />
    </item>
    
  </channel>
</rss>
