<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Access-Control on Crusader Research</title>
		<link>https://crusaderproxy.com/research/en/tags/access-control/</link>
		<description>Recent content in Access-Control on Crusader Research</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sat, 04 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://crusaderproxy.com/research/en/tags/access-control/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>IDOR lives in the second identifier: finding BOLA with two-account Shadow Replay</title>
				<link>https://crusaderproxy.com/research/en/posts/finding-idor-bola-with-shadow-replay/</link>
				<pubDate>Sat, 04 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://crusaderproxy.com/research/en/posts/finding-idor-bola-with-shadow-replay/</guid>
				<description>&lt;p&gt;Every IDOR tutorial hands you the same drill: find &lt;code&gt;/api/orders/48210&lt;/code&gt;, change it to &lt;code&gt;48211&lt;/code&gt;, look for a &lt;code&gt;200&lt;/code&gt;. That drill trains you to attack the one identifier the application is most likely to check. The primary key in the URL path is where the framework&amp;rsquo;s &lt;code&gt;@authorize&lt;/code&gt; annotation lives, where the ORM scopes the query, where the review focused. It&amp;rsquo;s the honeypot. You fuzz it, get &lt;code&gt;403&lt;/code&gt;s, call the endpoint safe, and walk right past the bug.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
