<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>XSS on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/xss/</link><description>Recent content in XSS on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 15 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/xss/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 5: Deep Dive into Cross-Site Scripting (XSS) Exploitation and Prevention</title><link>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/xss-exploitation-prevention/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/xss-exploitation-prevention/</guid><description>&lt;h2 id="introduction-to-the-xss-deep-dive"&gt;Introduction to the XSS Deep Dive&lt;/h2&gt;
&lt;p&gt;Welcome back, future security master! In the previous chapters, we laid the groundwork for understanding the web&amp;rsquo;s architecture and the attacker&amp;rsquo;s mindset. Now, it&amp;rsquo;s time to roll up our sleeves and dive deep into one of the most pervasive and often misunderstood web vulnerabilities: Cross-Site Scripting, or XSS.&lt;/p&gt;
&lt;p&gt;XSS isn&amp;rsquo;t just a simple &amp;ldquo;inject an alert box&amp;rdquo; trick; it&amp;rsquo;s a powerful vulnerability that can lead to session hijacking, data theft, website defacement, and even full control over a user&amp;rsquo;s browser session. Understanding XSS, from its core mechanics to advanced exploitation techniques and robust prevention strategies, is absolutely critical for anyone building or securing web applications in 2026.&lt;/p&gt;</description></item><item><title>Chapter 7: Cross-Site Scripting (XSS): Stored, Reflected, DOM-based</title><link>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/xss-attacks-prevention/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/xss-attacks-prevention/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, future security champion! In previous chapters, we laid the groundwork for understanding the attacker&amp;rsquo;s mindset and the importance of security. Now, we&amp;rsquo;re diving into one of the most common and impactful web vulnerabilities: Cross-Site Scripting, or XSS. It&amp;rsquo;s so prevalent it consistently ranks high on the OWASP Top 10 list (currently A03:2021-Injection).&lt;/p&gt;
&lt;p&gt;This chapter will demystify XSS. We&amp;rsquo;ll explore its different flavors – Stored, Reflected, and DOM-based – understanding how each works internally and how attackers exploit them. More importantly, we&amp;rsquo;ll equip you with the knowledge and practical skills to safely reproduce these vulnerabilities in a controlled environment and, crucial for a developer, implement effective prevention mechanisms. Get ready to write some secure code and protect your users!&lt;/p&gt;</description></item><item><title>Chapter 8: Cross-Site Request Forgery (CSRF) &amp;amp; Server-Side Request Forgery (SSRF)</title><link>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/csrf-ssrf-attacks/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/csrf-ssrf-attacks/</guid><description>&lt;h2 id="chapter-8-cross-site-request-forgery-csrf--server-side-request-forgery-ssrf"&gt;Chapter 8: Cross-Site Request Forgery (CSRF) &amp;amp; Server-Side Request Forgery (SSRF)&lt;/h2&gt;
&lt;p&gt;Welcome back, future security champion! In our previous chapters, we&amp;rsquo;ve explored how attackers can inject malicious code directly into your users&amp;rsquo; browsers (XSS) and how to protect against it. Now, we&amp;rsquo;re going to tackle two more insidious forms of attack that trick either the user&amp;rsquo;s browser or your server itself into performing unintended actions: Cross-Site Request Forgery (CSRF) and Server-Side Request Forgery (SSRF).&lt;/p&gt;</description></item><item><title>Chapter 10: Frontend Security: Protecting Your Application and Users</title><link>https://ai-blog.noorshomelab.dev/react-production-guide-2026/frontend-security-xss-csp/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/react-production-guide-2026/frontend-security-xss-csp/</guid><description>&lt;h2 id="chapter-10-frontend-security-protecting-your-application-and-users"&gt;Chapter 10: Frontend Security: Protecting Your Application and Users&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 10! As you build increasingly complex and interactive React applications, it&amp;rsquo;s paramount to remember that security isn&amp;rsquo;t just a backend concern—it&amp;rsquo;s a full-stack responsibility. The frontend, often the first point of interaction for your users, is a critical battleground for safeguarding data, maintaining user trust, and protecting your application&amp;rsquo;s integrity.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll dive deep into essential frontend security practices for modern React applications. You&amp;rsquo;ll learn how to defend against common vulnerabilities like Cross-Site Scripting (XSS), implement robust Content Security Policies (CSP), make informed decisions about secure data storage, and understand the risks and mitigations associated with third-party scripts. By the end, you&amp;rsquo;ll have a strong foundation for building more resilient and trustworthy React applications.&lt;/p&gt;</description></item><item><title>Chapter 12: Frontend Attack Surfaces: Securing React and Angular Applications</title><link>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/frontend-react-angular-security/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/frontend-react-angular-security/</guid><description>&lt;h2 id="chapter-12-frontend-attack-surfaces-securing-react-and-angular-applications"&gt;Chapter 12: Frontend Attack Surfaces: Securing React and Angular Applications&lt;/h2&gt;
&lt;p&gt;Welcome back, future security master! In our journey through advanced web application security, we&amp;rsquo;ve explored many server-side vulnerabilities and exploitation techniques. Now, it&amp;rsquo;s time to shift our focus to the client side – the modern frontend. With the rise of Single Page Applications (SPAs) built with frameworks like React and Angular, a significant portion of application logic, data handling, and user interaction now happens directly in the user&amp;rsquo;s browser. This shift creates new and often overlooked attack surfaces.&lt;/p&gt;</description></item><item><title>Chapter 13: Security Considerations in HTMX Applications</title><link>https://ai-blog.noorshomelab.dev/htmx-mastery-2025/security-considerations/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/htmx-mastery-2025/security-considerations/</guid><description>&lt;p&gt;Welcome back, fellow web artisan!&lt;/p&gt;
&lt;p&gt;In our journey to master HTMX, we&amp;rsquo;ve explored how it empowers us to build dynamic, interactive web experiences with minimal JavaScript. We&amp;rsquo;ve focused on creating features, enhancing user experience, and streamlining development. But as Uncle Ben famously said, &amp;ldquo;With great power comes great responsibility.&amp;rdquo; And in the world of web development, that responsibility often boils down to one critical aspect: &lt;strong&gt;security&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This chapter isn&amp;rsquo;t about scaring you, but about empowering you with the knowledge to build robust and secure HTMX applications. We&amp;rsquo;ll dive into the most common web security threats and, more importantly, how HTMX applications can effectively defend against them. We&amp;rsquo;ll learn why security is primarily a server-side concern, even when HTMX is doing the heavy lifting on the frontend, and how to implement best practices to protect your users and your data.&lt;/p&gt;</description></item><item><title>Chapter 14: Client-Side Security for React Applications</title><link>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/react-security-best-practices/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/react-security-best-practices/</guid><description>&lt;h2 id="introduction-to-client-side-security-in-react"&gt;Introduction to Client-Side Security in React&lt;/h2&gt;
&lt;p&gt;Welcome back, future security champions! In our journey so far, we&amp;rsquo;ve explored the foundational principles of web security, delved into the attacker&amp;rsquo;s mindset, and dissected the notorious OWASP Top 10. We&amp;rsquo;ve learned that security is a multi-layered defense, and while server-side protection is crucial, a robust application also demands strong client-side defenses.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to put on our React developer hats and focus specifically on securing our frontend applications. React is incredibly popular, and its component-based architecture and virtual DOM offer some inherent security advantages, but also introduce unique considerations. We&amp;rsquo;ll explore common client-side vulnerabilities like Cross-Site Scripting (XSS) and Cross-Site Request Forgery (CSRF) from a React perspective, understand how to handle authentication tokens securely, manage state safely, and interact with APIs responsibly.&lt;/p&gt;</description></item><item><title>Chapter 15: Client-Side Security for Angular Applications</title><link>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/angular-security-best-practices/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/angular-security-best-practices/</guid><description>&lt;h2 id="introduction-fortifying-your-angular-frontend"&gt;Introduction: Fortifying Your Angular Frontend&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 15! After delving into the foundational principles of web security, threat modeling, and common vulnerabilities, it&amp;rsquo;s time to bring that knowledge directly to your code. In this chapter, we&amp;rsquo;re shifting our focus to the client side, specifically on how to build highly secure applications using Angular, one of the most popular modern frontend frameworks.&lt;/p&gt;
&lt;p&gt;As web developers, we often focus on functionality and user experience. However, a beautiful and feature-rich application can quickly become a liability if it&amp;rsquo;s not secure. Client-side security is paramount because it&amp;rsquo;s the first line of defense against many common attacks, protecting your users&amp;rsquo; data and maintaining the integrity of your application. While server-side security is non-negotiable, a robust client-side implementation significantly reduces the attack surface.&lt;/p&gt;</description></item><item><title>Chapter 16: Frontend Security: CSP, XSS, and Token Storage</title><link>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/frontend-security/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/frontend-security/</guid><description>&lt;h2 id="chapter-16-frontend-security-csp-xss-and-token-storage"&gt;Chapter 16: Frontend Security: CSP, XSS, and Token Storage&lt;/h2&gt;
&lt;p&gt;Welcome back, future Angular security guru! In the intricate world of web development, building robust features is only half the battle. The other, equally critical half is ensuring those features are secure. Neglecting security is like building a beautiful house with no locks on the doors – it might look great, but it&amp;rsquo;s an open invitation for trouble.&lt;/p&gt;
&lt;p&gt;This chapter dives deep into crucial frontend security practices for your Angular applications, leveraging the latest standalone architecture. We&amp;rsquo;ll unravel the mysteries of common attack vectors like Cross-Site Scripting (XSS) and explore how Angular&amp;rsquo;s built-in tools, such as &lt;code&gt;DomSanitizer&lt;/code&gt;, become your first line of defense. We&amp;rsquo;ll then elevate our security posture with Content Security Policy (CSP), a powerful browser-level mechanism. Finally, we&amp;rsquo;ll tackle the ever-present challenge of securely storing sensitive authentication tokens, weighing the trade-offs between various approaches. By the end of this chapter, you&amp;rsquo;ll not only understand these concepts but also know how to implement them effectively, giving you the confidence to build truly secure Angular applications.&lt;/p&gt;</description></item><item><title>Chapter 16: Hands-On Project: Building a Secure React E-commerce Frontend</title><link>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/secure-react-ecommerce-project/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/secure-react-ecommerce-project/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 16! After exploring the theoretical foundations of web security, understanding attacker mindsets, and dissecting the OWASP Top 10, it&amp;rsquo;s time to get our hands dirty. In this chapter, we&amp;rsquo;re going to apply all that knowledge by building a secure frontend for a hypothetical e-commerce application using React. This isn&amp;rsquo;t just about making things work; it&amp;rsquo;s about making them work &lt;em&gt;securely&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;Why an e-commerce frontend? Because these applications handle sensitive user data, payment information, and authentication, making them prime targets for various attacks. By building one with security in mind from the ground up, you&amp;rsquo;ll gain invaluable practical experience in defending against common vulnerabilities. We&amp;rsquo;ll focus on client-side aspects, assuming a secure backend handles server-side logic and data storage.&lt;/p&gt;</description></item><item><title>Chapter 17: Hands-On Project: Securing an Existing Angular Dashboard</title><link>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/secure-angular-dashboard-project/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/secure-angular-dashboard-project/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, future security champions! In our previous chapters, we&amp;rsquo;ve explored the foundational principles of web security, delved into the attacker&amp;rsquo;s mindset, and dissected the notorious OWASP Top 10 vulnerabilities. We&amp;rsquo;ve even touched upon secure coding practices for modern frontend frameworks. Now, it&amp;rsquo;s time to put all that knowledge into action!&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to tackle a common real-world scenario: securing an &lt;em&gt;existing&lt;/em&gt; Angular dashboard application. Imagine you&amp;rsquo;ve inherited a functional dashboard that displays user-specific data, but it wasn&amp;rsquo;t built with security as a top priority. Your mission, should you choose to accept it, is to fortify this application against common threats. We&amp;rsquo;ll focus on implementing robust authentication, protecting against Cross-Site Scripting (XSS) and Cross-Site Request Forgery (CSRF), and ensuring secure communication with our backend API.&lt;/p&gt;</description></item><item><title>Security Best Practices in Angular System Design</title><link>https://ai-blog.noorshomelab.dev/angular-system-design-2026-guide/security-best-practices/</link><pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-system-design-2026-guide/security-best-practices/</guid><description>&lt;h2 id="introduction-to-angular-security"&gt;Introduction to Angular Security&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 18! As you build increasingly complex Angular applications, especially those managing sensitive data or user interactions, security transitions from a mere checklist item to a fundamental pillar of your system design. A single vulnerability can compromise user data, disrupt services, or damage your organization&amp;rsquo;s reputation.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll dive deep into securing modern Angular applications. We&amp;rsquo;ll explore common web vulnerabilities, understand Angular&amp;rsquo;s built-in defenses, and learn how to implement robust authentication, authorization, and secure communication patterns. Our goal is not just to fix issues, but to design with security in mind from the ground up, ensuring your applications are resilient against evolving threats.&lt;/p&gt;</description></item><item><title>Chapter 26: Security Best Practices for React Applications</title><link>https://ai-blog.noorshomelab.dev/react-mastery-2026/chapter-26-security-best-practices/</link><pubDate>Sat, 31 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/react-mastery-2026/chapter-26-security-best-practices/</guid><description>&lt;h2 id="introduction-protecting-your-react-applications"&gt;Introduction: Protecting Your React Applications&lt;/h2&gt;
&lt;p&gt;Welcome to one of the most critical chapters in our React journey: &lt;strong&gt;Security Best Practices&lt;/strong&gt;! As you become more proficient in building complex React applications, it&amp;rsquo;s absolutely vital to understand how to protect them from malicious attacks and common vulnerabilities. Think of it like building a beautiful, sturdy house – you wouldn&amp;rsquo;t forget to put locks on the doors, would you?&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll dive into the world of frontend security. We&amp;rsquo;ll explore common threats that React applications face, understand how React&amp;rsquo;s architecture helps (and sometimes requires extra care), and learn practical strategies to safeguard your code and your users&amp;rsquo; data. While backend security is paramount, a robust frontend security posture adds crucial layers of defense.&lt;/p&gt;</description></item><item><title>How Content Security Policy (CSP) Works: Deep Dive into Internals</title><link>https://ai-blog.noorshomelab.dev/how-it-works/content-security-policy-internals/</link><pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/how-it-works/content-security-policy-internals/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the intricate landscape of web security, protecting users from malicious attacks is a paramount concern. Content Security Policy (CSP) stands as a critical defense mechanism, acting as an additional layer of security to mitigate various code injection threats. It&amp;rsquo;s not merely a &amp;ldquo;firewall&amp;rdquo; but a sophisticated agreement between a web server and a browser, dictating precisely which resources the browser is permitted to load and execute for a given page.&lt;/p&gt;</description></item></channel></rss>