Windsurf security

Windsurf Generated API Routes Without Auth Middleware

Windsurf's Cascade generated API routes and server endpoints that process requests without verifying the user is authenticated or authorized. Anyone who knows the URL can access, modify, or delete data without logging in.

This happens frequently when Cascade creates new CRUD endpoints, admin routes, or data export functionality. The generated handlers focus on the business logic but skip the authentication and authorization layer entirely. Your app may have a login page, but the API behind it is wide open.

You might discover this when testing your API directly with curl or Postman and realizing it returns data without any authentication header, or when a user accesses another user's data by changing an ID in the URL.

Error Messages You Might See

200 OK (but should be 401 Unauthorized) Data returned without authentication header User A can see User B's records No authorization header required
200 OK (but should be 401 Unauthorized)Data returned without authentication headerUser A can see User B's recordsNo authorization header required

Common Causes

  • No middleware applied to new routes — Cascade generated route handlers but didn't wrap them with your existing auth middleware
  • Auth check missing on individual endpoints — Some routes have auth, others don't, because they were generated in separate Cascade sessions
  • No authorization checks — Routes verify the user is logged in but don't check if they have permission to access the specific resource
  • Public endpoints exposing private data — API routes intended for internal use are accessible without authentication
  • Missing user scoping on queries — Database queries return all records instead of filtering by the authenticated user's ID

How to Fix It

  1. Audit all your routes — List every API endpoint in your app and mark which ones require authentication. Any endpoint that reads or writes user data must be protected
  2. Apply auth middleware globally — Set up authentication middleware at the router level so all routes are protected by default, then explicitly mark public routes
  3. Add authorization checks — After verifying identity, check that the user has permission to access the specific resource (e.g., only the owner can edit their profile)
  4. Scope all database queries — Always filter queries by the authenticated user's ID: WHERE user_id = $currentUser instead of returning all rows
  5. Test with unauthenticated requests — Use curl or Postman to hit every endpoint without an auth token and verify you get 401 responses
  6. Enable Supabase RLS if applicable — Turn on Row Level Security and create policies that restrict data access at the database level

Real developers can help you.

Pratik Pratik SWE with 15+ years of experience building and maintaining web apps and extensive BE infrastructure David Olverson David Olverson Solo dev shipping production apps with AI-assisted development. I specialize in rescuing broken Lovable/Bolt/Cursor builds and taking them to production. 10+ apps shipped including SaaS CRMs, gaming platforms, real estate tools, and Discord bots. Stack: Next.js 16, TypeScript, Tailwind CSS, FastAPI, PostgreSQL, Prisma. I use Claude Code with 50+ custom skills for rapid delivery. Average turnaround: 2-4 weeks from broken prototype to production. MFox MFox Full-stack professional senior engineer (15+years). Extensive experience in software development, qa, and IP networking. Krishna Sai Kuncha Krishna Sai Kuncha Experienced Professional Full stack Developer with 8+ years of experience across react, python, js, ts, golang and react-native. Developed inhouse websearch tooling for AI before websearch was solved : ) zipking zipking I am a technologist and product builder dedicated to creating high-impact solutions at the intersection of AI and specialized markets. Currently, I am focused on PropScan (EstateGuard), an AI-driven SaaS platform tailored for the Japanese real estate industry, and exploring the potential of Archify. As an INFJ-T, I approach development with a "systems-thinking" mindset—balancing technical precision with a deep understanding of user needs. I particularly enjoy the challenge of architecting Vertical AI SaaS and optimizing Small Language Models (SLMs) to solve specific, real-world business problems. Whether I'm in a CTO-level leadership role or hands-on with the code, I thrive on building tools that turn complex data into actionable value. Luca Liberati Luca Liberati I work on monoliths and microservices, backends and frontends, manage K8s clusters and love to design apps architecture Jacek Rozanski Jacek Rozanski Senior PHP/Symfony developer and DevOps engineer with 20+ years of professional experience, running opcode.pl (web development agency, est. 2004). Day job: I'm the sole backend developer at merketing company where I own and maintain 11 PHP/Symfony microservices on AWS (ECS Fargate, RDS, S3, CloudFront), handle the full CI/CD pipeline (Bitbucket Pipelines, Docker), and manage monitoring with Sentry and CloudWatch. These services handle high request volumes in production every month. What I bring to AI-built apps: - I audit and fix security issues (OWASP methodology), performance bottlenecks, and architectural problems in codebases generated by Cursor, Claude Code, Lovable, Bolt, and v0 - I refactor AI-generated prototypes into production-grade applications with proper error handling, testing, and clean architecture (SOLID, DDD, hexagonal architecture) - I set up the infrastructure AI tools don't touch: AWS hosting, CI/CD pipelines, automated deployments, database optimization, monitoring, and alerting - I integrate external services: payment providers, email systems, partner APIs, SSO/auth Tech stack: PHP 8.x, Symfony, React, Next.js, PostgreSQL, MySQL, Docker, AWS (ECS, RDS, S3, SQS/SNS, CloudFront), Terraform, Supabase. I also use AI tools daily (Claude Code, Cursor) in my own workflow, so I understand both the strengths and the gaps in AI-generated code. Based in Poland (CET timezone). Available for async work and calls during EU/US business hours. Simon A. Simon A. I'm a backend developer building APIs, emulators, and interactive game systems. Professionally, I've developed Java/Spring reporting solutions, managed relational and NoSQL databases, and implemented CI/CD workflows. rayush33 rayush33 JavaScript (React.js, React Native, Node.js) Developer with demonstrated industry experience of 4+ years, actively looking for opportunities to hone my skills as well as help small-scale business owners with solutions to technical problems Daniel Vázquez Daniel Vázquez Software Engineer with over 10 years of experience on Startups, Government, big tech industry & consulting.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

How do I know which endpoints are unprotected?

Use curl or Postman to make requests to each API endpoint without any authentication headers. Any endpoint that returns 200 instead of 401 is unprotected. Also review your route files for handlers that don't reference auth middleware.

Should I protect every single endpoint?

Almost every endpoint should require authentication. The exceptions are typically: login/signup, password reset, public content pages, health checks, and webhook receivers. Everything that touches user data must be protected.

Related Windsurf Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help