<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog on Robin Roy</title>
    <link>https://robinroy.xyz/blog/</link>
    <description>Recent content in Blog on Robin Roy</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 02 Aug 2026 06:42:18 +0530</lastBuildDate>
    <atom:link href="https://robinroy.xyz/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Entry, Escalation, Persistence: Taking Apart Frappe&#39;s Document Follow</title>
      <link>https://robinroy.xyz/blog/frappe-document-follow-vulnerability/</link>
      <pubDate>Sun, 02 Aug 2026 06:42:18 +0530</pubDate>
      <guid>https://robinroy.xyz/blog/frappe-document-follow-vulnerability/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/frappe/frappe/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Frappe&lt;/a&gt; is an open-source framework used to build software like &lt;a href=&#34;https://github.com/frappe/erpnext/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;ERPNext&lt;/a&gt;, a widely deployed open-source ERP. My job is mostly working with apps built on this framework. During one session in May I noticed some peculiarities with how frappe&amp;rsquo;s document follow feature is implemented. Curious, I dug deep to find a chain of three authorization failures - one at the object level, one at the field level, and one in the lifetime of the grant itself - that allowed an attacker to access data they aren&amp;rsquo;t authorized to.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
