<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Xml on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</title><link>https://blog.lameiro0x.com/tags/xml/</link><description>Recent content in Xml on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</description><generator>Hugo -- 0.161.1</generator><language>en-us</language><lastBuildDate>Fri, 17 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.lameiro0x.com/tags/xml/index.xml" rel="self" type="application/rss+xml"/><item><title>Web attacks</title><link>https://blog.lameiro0x.com/notes/exploitation/web-attacks/</link><pubDate>Fri, 17 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.lameiro0x.com/notes/exploitation/web-attacks/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;This topic brings together three very common web attack families: HTTP verb tampering, insecure direct object references, and XML external entity injection. They look different on the surface, but all three usually come from the same core weakness: the application trusts client-controlled input more than it should, and the backend does not enforce validation and authorization consistently. In practice, this means a tester can often move from a small logic flaw to data exposure, privilege escalation, or even server-side code execution.&lt;/p&gt;</description></item></channel></rss>