<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Html-Injection on Dedsec</title><link>https://dedsec-2.github.io/tags/html-injection/</link><description>Recent content in Html-Injection on Dedsec</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 09 May 2026 14:00:00 +0200</lastBuildDate><atom:link href="https://dedsec-2.github.io/tags/html-injection/index.xml" rel="self" type="application/rss+xml"/><item><title>Breaking In Without a Key: Chaining Client-Side Auth Into Stored HTML Injection</title><link>https://dedsec-2.github.io/posts/client-side-auth-bypass-injection-chain/</link><pubDate>Sat, 09 May 2026 14:00:00 +0200</pubDate><guid>https://dedsec-2.github.io/posts/client-side-auth-bypass-injection-chain/</guid><description>&lt;h2 id="-intro">$ ./intro&lt;/h2>
&lt;p>Some targets look locked down at first glance. Login page, redirect on every protected URL, role-gated sections marked &amp;ldquo;Not Authorized.&amp;rdquo; You open Burp, run a few requests, and think &lt;em>&amp;ldquo;this is going to be a long day.&amp;rdquo;&lt;/em>&lt;/p>
&lt;p>Then you notice that none of the HTTP responses ever return a &lt;code>302&lt;/code>. And your whole afternoon changes.&lt;/p>
&lt;p>This is a writeup of a web application penetration test against an internal manufacturing dashboard — a platform used by engineers, factory leads, and regional teams to track production data, file technical issues, and manage order queues. The application had a multi-role access model with pages supposedly gated behind authorization checks. What it did not have was any of those checks running on the server.&lt;/p></description></item></channel></rss>