FixVibe

// 프로브 / 스포트라이트

반사형 크로스사이트 스크립팅 (XSS)

조용한 탈취: 검증되지 않은 매개변수 하나가 사용자 브라우저에서 공격자 코드를 실행해요.

What it is

Reflected Cross-Site Scripting is one of the oldest bugs on the web — and one of the most stubborn. Despite decades of warnings, modern apps keep shipping it. The reason is simple: the browser cannot tell which `<script>` tag was put there by your developers and which was injected by a malicious URL parameter. Both run with the same trust as the rest of your code, which means access to cookies, local storage, the DOM, and any session your visitor has open in that tab.

How it happens

Reflected XSS appears when request input is returned in HTML in a context the browser can execute. Attackers can turn that behavior into links or form submissions that run script in another user's session.

What an attacker gets

An attacker who runs JavaScript in your origin can steal session cookies (unless they're HttpOnly), exfiltrate data the user can see, perform actions as the user (transfer funds, change passwords, post content), key-log inputs on the page, or pivot into a phishing overlay convincing enough that the user happily re-enters credentials.

// what fixvibe reports

What FixVibe reports

Runs in active scans of a domain you have verified you own, on Hobby and above. Each finding shows the affected URL or host, its severity and fix steps you can paste into your AI coding tool.

How to fix it

Treat all user input as hostile and apply context-aware output encoding when rendering: HTML entities for body content, attribute escaping for HTML attributes, JavaScript string escaping for inline scripts, URL encoding for href/src. Modern frameworks (React, Vue, Svelte) escape by default — opt-out paths like dangerouslySetInnerHTML are the usual culprits, and they should run user input through DOMPurify first. Add a strict Content Security Policy with no `unsafe-inline` and a per-request nonce so injected scripts cannot execute even if the encoding fails. Set HttpOnly + Secure + SameSite=Lax on every session cookie so a successful XSS at least can't read your auth token. Defense in depth.

Key takeaway

XSS prevention is not a single fix — it's a stack. Modern templating, strict CSP, HttpOnly cookies, and never trusting user input are each one layer. Skip any one of them and the next one carries the load.

// 내 앱에서 직접 실행해보세요

FixVibe가 지켜보는 동안 계속 배포하세요.

Verify you own the domain, then run active checks alongside the passive ones.

능동 프로브
138
이 카테고리에서 실행되는 테스트
모듈
58
전용 능동 프로브 검사
verified domains
130+
active checks after verification
Verify your domain →

// 최신 체크 · 실용적인 수정 · 자신 있게 배포

반사형 크로스사이트 스크립팅 (XSS): what it is and how to fix it · FixVibe