XSS, CSRF, CORS & HTTPS Separate browser threats and match mitigations to the correct security problem
Phase 16 - Authentication Fundamentals Volume 05 - Authentication & Security
v
v
Phase 16 builds the security mental model before any Supabase Auth integration code is introduced.
XSS, CSRF, and CORS are different problems Authentication bugs often come from mixing browser security concepts. These mechanisms overlap in consequences but solve different threats.
XSS Can attacker-controlled JavaScript execute in our origin?
CSRF Can another site cause the browser to send an authenticated request the user did not intend?
CORS May browser JavaScript read/call a cross-origin resource under the server CORS policy?
HTTPS/TLS Can network attackers read/modify traffic in transit?
Authentication Who is the caller?
Authorization May that caller perform this action?
Cookie authentication and CSRF Browsers automatically attach eligible cookies. That convenience creates CSRF risk: another site may be able to trigger a request while the victim browser includes its authenticated cookie. SameSite is an important mitigation, but applications may also need CSRF tokens or origin checks depending on architecture and request patterns.
v
v
v
v
Cookie authentication requires cross-site request reasoning.
JavaScript-readable tokens and XSS If an access or refresh token is stored where application JavaScript can read it, injected JavaScript can potentially exfiltrate it. HttpOnly cookies reduce direct token theft through JavaScript, but they do not magically solve all XSS impact because malicious scripts can still issue actions as the user while running in the origin.
CORS is not authentication CORS is a browser-enforced cross-origin access policy. It does not prove who a request came from. Non-browser clients do not rely on browser CORS enforcement. An API with permissive CORS still needs authentication and authorization; an API with strict CORS is not automatically secure.
Bearer tokens, cookies, passwords, and authentication codes must be protected in transit. Secure cookie semantics also depend on HTTPS in production.
XSS CSRF CORS and HTTPS matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “XSS CSRF CORS and HTTPS” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: User intent → UI boundary → API contract → business rule → persistence → observable result. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Authentication threat/flow diagram explaining what the browser stores, what servers verify, and what happens when credentials expire.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
OPTIONS /tasks HTTP/1.1
Origin: http://localhost:3000
Access-Control-Request-Method: POST
Access-Control-Request-Headers: authorization,content-type
HTTP/1.1 204 No Content
Access-Control-Allow-Origin: http://localhost:3000Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “XSS CSRF CORS and HTTPS” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Draw password login without writing code and mark where plain-text password may exist temporarily.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Confusing hidden UI with authorization
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.