Skip to content

Interview question · Application & API Security

Why does an XSS vulnerability defeat CSRF tokens, SameSite cookies and HttpOnly? What actually limits the damage?

CSRF defences stop other sites from acting as the user. XSS is not another site: it is code running inside yours, with everything your own pages can do.

mediumNewPreparation tags: Google, Meta, MicrosoftUpdated Nov 2026

CSRF defences stop other sites from acting as the user. XSS is not another site: it is code running inside yours, with everything your own pages can do.

Make your first attempt

What would you say before reading the answer?

  1. 01 State the assumptions your answer depends on.
  2. 02 Explain the mechanism and choose a control.
  3. 03 Name a condition that would change your decision.

The worked answer includes an approach, scoring criteria and follow-up questions. Compare the reasoning with your own.

10 answers per topic instead of 5, plus saved progress and bookmarks · costs nothingor unlock all 529 remaining answers · $25

Every worked answer in all 17 topics, every lesson in every course, the full concept curriculum, the complete practice-test bank, and the downloadable security field guides.

6 months · One payment · No auto-renewal

What if · the follow-ups in this answer

The answer works through 6 follow-ups like an interviewer would

An app has strong CSRF tokens and SameSite cookies, but a reviewer finds a stored XSS bug and the team argues CSRF protection limits the impact.

  1. What do CSRF defences rely on?
  2. Why does XSS defeat them?
  3. What about HttpOnly cookies?
  4. What does that mean for severity?
  5. What actually limits XSS impact?
  6. How would you respond to the team's argument?

Each rung has a nudge, a model answer, the principle that carries over and the weak answer to avoid. Premium opens every answer and ladder.

UP NEXT ON YOUR JOURNEY
DISCUSSION · 0

No comments yet. Share a correction or a different way to answer it.