v0 security

API Route Exposing Sensitive Data in Response

Your v0-generated Next.js API route is returning sensitive data in its JSON response that should never reach the client. Internal database IDs, user emails, hashed passwords, API keys, or internal configuration values are being serialized and sent to the browser because the route handler returns the full database record without filtering fields.

This is especially dangerous when v0 scaffolds CRUD endpoints that use Prisma's findMany or findUnique without a select clause, causing every column in the table to be included in the response payload.

Attackers can inspect network responses in DevTools or call your API directly to harvest sensitive information, leading to data breaches and compliance violations.

Error Messages You Might See

Sensitive data exposure detected in API response Password hash visible in /api/users response Internal server configuration leaked via API User PII exposed without authorization check
Sensitive data exposure detected in API responsePassword hash visible in /api/users responseInternal server configuration leaked via APIUser PII exposed without authorization check

Common Causes

  • No field filtering on queries — Prisma findMany/findUnique returns all columns by default, including password hashes and internal flags
  • Spreading full user objects — v0 generated return NextResponse.json(user) without picking safe fields
  • Environment variables in responses — process.env values accidentally included in API response during debugging
  • Nested relations exposing data — Prisma include statements pulling related records with sensitive fields
  • No response serialization layer — missing DTO or transform step between database and response

How to Fix It

  1. Add Prisma select clauses — replace findMany() with findMany({ select: { id: true, name: true, avatar: true } }) to whitelist safe fields
  2. Create response DTOs — build a toPublicUser() function that strips sensitive fields before returning
  3. Audit all API routes — search your codebase for NextResponse.json and verify every response payload is sanitized
  4. Add middleware validation — create a response sanitizer middleware that strips known sensitive field names
  5. Use Zod output schemas — define Zod schemas for API responses and parse through them before returning

Real developers can help you.

Costea Adrian Costea Adrian Embedded Engineer specilizing in perception systems. Latest project was a adas camera calibration system. 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 : ) Omar Faruk Omar Faruk As a Product Engineer at Klasio, I contributed to end-to-end product development, focusing on scalability, performance, and user experience. My work spanned building and refining core features, developing dynamic website templates, integrating secure and reliable payment gateways, and optimizing the overall system architecture. I played a key role in creating a scalable and maintainable platform to support educators and learners globally. I'm enthusiastic about embracing new challenges and making meaningful contributions. 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. Jared Hasson Jared Hasson Full time lead founding dev at a cyber security saas startup, with 10 yoe and a bachelor's in CS. Building & debugging software products is what I've spent my time on for forever Victor Denisov Victor Denisov Developer Basel Issmail Basel Issmail ’m a Senior Full-Stack Developer and Tech Lead with experience designing and building scalable web platforms. I work across the full development lifecycle, from translating business requirements into technical architecture to delivering reliable production systems. My work focuses on modern web technologies, including TypeScript, Angular, Node.js, and cloud-based architectures. I enjoy solving complex technical problems and helping teams turn product ideas and prototypes into working platforms that can grow and scale. In addition to development, I often collaborate closely with product managers, business analysts, designers, and QA teams to ensure that solutions align with both technical and business goals. I enjoy working with startups and product teams where I can contribute both as a hands-on engineer and as a technical partner in designing and delivering impactful software. Rudra Bhikadiya Rudra Bhikadiya I build and fix web apps across Next.js, Node.js, and DBs. Comfortable jumping into messy code, broken APIs, and mysterious bugs. If your project works in theory but not in reality, I help close that gap. Matthew Butler Matthew Butler Systems Development Engineer @ Amazon Web Services AUXLE AUXLE I am a Full Stack Developer experienced in building Websites, Web apps and Cross Platform Mobile Apps for Startups and Companies.

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 find all exposed API routes?

Search your app/api directory for NextResponse.json calls. Check each one to ensure it uses Prisma select or maps through a DTO before returning data.

Should I use select or omit in Prisma?

Use select for whitelisting safe fields. Prisma omit is available in newer versions but select is more explicit and safer by default.

How do I prevent this in future v0 generations?

Add a project rule in v0 that instructs it to always use select clauses in Prisma queries and never return raw database objects.

Related v0 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