Cursor app security audit
Cursor writes whatever you ask for, so the risks follow your code: secret passwords (called keys) saved into the code's history, requests answered without checking whose data it is, and data rules that are too open. A security audit of a Cursor-built app reads your code and gives you a Cursor prompt for each fix.
Report in 48 hours or you're not charged. Your card is only held until the report is delivered.
Start with the free scan
- Open scan.getnordik.com and paste the link to your app.
- Press "Scan my app". There is no sign-up, and nothing to place on your app.
- Get hints in under a minute about what your app shows to the outside. The scan opens only what any visitor's device opens; it never signs in or writes anything.
What the $129 audit gives you
- A plain-words report that says what each problem means for your users, and how serious it is, without security jargon.
- A technical report with the file and line of every finding, for you or a developer.
- A copy-paste fix prompt for every finding. Each fix prompt is written for Cursor's agent: the file and line, the change and the test that proves it. Where we could check a fix, you get the checked fix too.
- A "how to check it is fixed" step for each finding, and a free re-check after you fix.
- Money back if a confirmed finding is wrong.
The audit is AI-performed: it reads your code and the rules that guard your data, and it is not a penetration test.
Every audit is read by the owner before it reaches you.
The free scan works for every platform. Its hints point at where to look; the audit reads the code and confirms what is really there. For deeper checks you can show the app is yours with a one-time code. That step is optional.
What usually goes wrong in apps built with Cursor
Apps built with Cursor are often made with Next.js and Supabase, but they can be made with anything. You already have the folder that holds your code and its history (a repository), which is all the audit needs.
Secret passwords saved into the code's history
A repository remembers every saved version of your code. A settings file that holds keys (an .env file), or a key itself, that was saved once stays in that history even after you delete it. The fix is to replace the key with a new one, not only to remove the file.
Source: GitHub documentation: About secret scanning
Requests that trust whoever is asking
Every part of your app that answers a request should check who is asking and whether the data is theirs. An AI agent that adds a new one can easily leave that check out.
Source: Next.js documentation: How to think about data security; OWASP Authorization Cheat Sheet
Database rules left open from prototyping
A Supabase table of data with its protection (row-level security) off, or with a rule that allows everyone, can be read by any visitor.
Source: Supabase documentation: Row Level Security
Agent edits that went in unread
Cursor's agent can change many files at once, and its own documentation tells you to keep version control (a saved history of your code) so you can go back. A review of the final code catches what slipped through.
Source: Cursor documentation: Agent security
How ordering works
- Share your repository on GitHub, GitLab or Bitbucket with us, or send a zipped copy of it.
- Check out for $129. Your card is held, not charged.
- Your report arrives within 48 hours. The charge happens only then; if it does not arrive in time, you are not charged.
Nordik App Audit supports every platform, and apps built with Cursor can order today.
A stack is the set of tools an app is built on. Before a report goes out, our checks for a stack must pass our own quality test. A stack that has passed is called qualified; for a stack not qualified yet, that work is done after you order.
We support every platform. Apps built with Cursor and any other stack are qualified on demand inside the same 48 hours, and if we cannot deliver a passing report in time, your hold is released and you pay nothing.
Qualification is per family. Next.js + Supabase: the newest re-check passed config headers errors (a measurement, not yet a promise); not yet measured after the newest re-check: route authorization, service role, object scoping, request trust, database policy, secrets (we still look there, but a clean result in them is not a pass).
Recall was met in route authorization, database policy, secrets, but high and critical findings from that run are still unchecked against a label, so we do not call them qualified. Today we do not promise any part of this stack as fully checked. Every report is held to the same quality check before it reaches you.
Questions
How do I check my Cursor-built app is secure before deploying?
Replace any secret password (key) that was ever saved into your code's history, check that every request checks whose data it is, and make sure your data rules are switched on. The free scan gives you hints from your app's public link; the $129 audit reads your code and lists each fix with a prompt.
Can I get my vibe-coded app audited without spending thousands?
Yes. The free scan costs nothing, and the full AI-performed audit is $129 one-time, with a free re-check after you fix. It is not a penetration test, and it is priced for builders.
What does the free scan of a Cursor app look at?
Only what your app already shows to anyone on the internet. You paste the link to your app and press one button, and in under a minute the scan gives you hints about what may be in public view by mistake. Showing the app is yours with a one-time code is optional and adds deeper checks. The scan never signs in, writes or submits anything, and it does not read your code. Hints are not findings: the audit reads the code to confirm them.
What do I get for $129?
A plain-words report and a technical report, a copy-paste fix prompt and a "how to check it is fixed" step for every finding, plus a free re-check after you fix. If a confirmed finding turns out to be wrong, you get your money back. It is a one-time price, not a subscription.
How fast is the report, and when am I charged?
Report in 48 hours or you are not charged. At checkout your card is only held; the charge happens when the report is delivered. Nordik App Audit supports every platform, and apps built with Cursor can order today. A stack is the set of tools an app is built on. Before a report goes out, our checks for a stack must pass our own quality test. A stack that has passed is called qualified; for a stack not qualified yet, that work is done after you order. We support every platform. Apps built with Cursor and any other stack are qualified on demand inside the same 48 hours, and if we cannot deliver a passing report in time, your hold is released and you pay nothing. What our own testing has measured so far is set out under "How ordering works" on this page.
Is this a penetration test?
No. It is not a penetration test, which tries, with your permission, to break into your running app. Nordik App Audit is an AI-performed audit: it reads your code and the rules that guard your data, and never attacks your app. Like any review it can miss things, which is why every finding comes with a way to check the fix yourself.
Sources
- GitHub documentation: About secret scanning, read 2026-11-16
- Next.js documentation: How to think about data security, read 2026-11-16
- OWASP Authorization Cheat Sheet, read 2026-11-16
- Supabase documentation: Row Level Security, read 2026-11-16
- Cursor documentation: Agent security, read 2026-11-16
Nordik is not affiliated with Cursor. Product names belong to their owners.