<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lfi on Fabrice's Blog</title><link>https://blog.redteamshell.com/tags/lfi/</link><description>Recent content in Lfi on Fabrice's Blog</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener">CC BY-NC 4.0&lt;/a></copyright><lastBuildDate>Wed, 16 Sep 2026 18:45:00 -0400</lastBuildDate><atom:link href="https://blog.redteamshell.com/tags/lfi/index.xml" rel="self" type="application/rss+xml"/><item><title>CWEE Path Notes — Module 1: Injection Attacks</title><link>https://blog.redteamshell.com/posts/2026/09/cwee-path-notes-module-1-injection-attacks/</link><pubDate>Wed, 16 Sep 2026 18:45:00 -0400</pubDate><guid>https://blog.redteamshell.com/posts/2026/09/cwee-path-notes-module-1-injection-attacks/</guid><description>&lt;p>&lt;img src="https://blog.redteamshell.com/images/cwee-m01-hero.jpg" alt="CWEE Module 01 Hero">&lt;/p>
&lt;p>This kicks off a series where I work through the &lt;strong>HTB Certified Web Exploitation Expert (CWEE)&lt;/strong> path — the &lt;em>Senior Web Penetration Tester&lt;/em> job-role path — one module at a time and write down what actually stuck. This is more of &amp;ldquo;here&amp;rsquo;s the reasoning and the things that bit me&amp;rdquo; — the point is the technique, not an answer key.&lt;/p>
&lt;p>Module 1 is &lt;strong>Injection Attacks&lt;/strong>, and it covers three of the less-glamorous injection classes that developers rarely defend against precisely because they&amp;rsquo;re less common: &lt;strong>XPath injection&lt;/strong>, &lt;strong>LDAP injection&lt;/strong>, and &lt;strong>HTML injection in PDF generation libraries&lt;/strong>. That obscurity is the whole opportunity — if an app touches XML, an LDAP directory, or a server-side PDF renderer, it&amp;rsquo;s often untested ground.&lt;/p></description></item></channel></rss>