<?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>Wordpress on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</title><link>https://blog.lameiro0x.com/tags/wordpress/</link><description>Recent content in Wordpress on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</description><generator>Hugo -- 0.161.1</generator><language>en-us</language><lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.lameiro0x.com/tags/wordpress/index.xml" rel="self" type="application/rss+xml"/><item><title>Attacking Common Applications</title><link>https://blog.lameiro0x.com/notes/exploitation/attacking-common-applications/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.lameiro0x.com/notes/exploitation/attacking-common-applications/</guid><description>&lt;h1 id="why-application-fingerprinting-matters"&gt;Why Application Fingerprinting Matters&lt;/h1&gt;
&lt;p&gt;Common enterprise applications deserve focused attention because they often expose far more than a normal website. A CMS, a CI/CD server, a ticketing portal, or a monitoring platform usually sits on top of sensitive data, administrative workflows, and privileged backend services. Even when the core application is well maintained, weak credentials, exposed admin panels, unsafe plugins, and risky default features can still create a direct path to code execution or lateral movement. For that reason, application fingerprinting is not just reconnaissance; it is the first step in understanding which attack paths are realistically available.&lt;/p&gt;</description></item></channel></rss>