Security Scanner forCursor Apps
We scanned 100 real Cursor-built apps. 67% had at least one critical vulnerability. IDOR, inverted auth, hardcoded secrets, and three CVEs published in 2025 alone.
The short answer
The Short Answer: Cursor Is Safe, But Its Code Isn’t
Cursor the editor is SOC 2 Type II certified and offers Privacy Mode to keep your code off its servers. The security risk isn't the tool — it's the code the tool generates.
A Stanford University study (Perry et al., 2024) found that developers using AI code assistants produce significantly less secure code, with roughly 45% of AI-assisted code containing vulnerabilities. Our own research confirms this: scanning 100 real Cursor-built repositories, we found 67% had at least one critical vulnerability, with an average of 3.2 security issues per app.
On top of code-level risks, three CVEs were published against Cursor in 2025:
- CVE-2025-54135 (CurXecute) — Malicious Slack messages processed by Cursor could rewrite MCP configs and execute arbitrary commands
- CVE-2025-54136 (MCPoison) — Shared repository configs enabled persistent team-wide compromise
- CVE-2025-59944 — Case-sensitivity bypass allowed attackers to modify protected configuration files
The bottom line: use Cursor for speed, but scan before you ship. Read our full analysis of 100 Cursor-built apps for the complete data.
Common vulnerabilities
Common Vulnerabilities in Cursor Projects
These are the security issues we find most frequently in codebases built with Cursor. For a full breakdown, see our vulnerabilities by platform reference.
IDOR with Sequential IDs
CriticalCursor frequently generates API routes using auto-incrementing IDs without ownership checks. An attacker changes /api/invoices/42 to /api/invoices/43 and accesses another user's data. Found in 43% of the 100 Cursor apps we scanned.
Inverted Auth Conditions
CriticalA single misplaced negation operator flips your auth logic: authenticated users get blocked, anonymous requests get through. We found this in 31% of Cursor-built apps. It passes manual testing because you test while logged in.
Frontend-Only Admin Checks
HighCursor generates admin panels where role checks only happen in React components. The API endpoints behind them accept requests from anyone. Present in 28% of scanned apps.
Hardcoded Secrets in Source
HighCursor pulls API keys from your context window and embeds them directly in code. These get committed to Git history permanently. According to GitGuardian, 12.8 million secrets were exposed on GitHub in 2024 alone. Found in 22% of our scanned repos.
MCP & Prompt Injection Risks
CriticalCVE-2025-54135 (CurXecute) showed that malicious content processed by Cursor can rewrite MCP configs and execute arbitrary commands. CVE-2025-54136 (MCPoison) enabled team-wide compromise through shared repository configs.
Auto-Run Code Execution
HighCursor ships with Workspace Trust disabled by default (CVE-2025-59944). A malicious .vscode/tasks.json in a cloned repo can execute code the moment you open the folder — no click required.
How ShipSafe Secures Your Cursor Project
Connect Your Repository
Link your GitHub repo or paste your code. ShipSafe supports any Cursor-generated project regardless of framework.
Automated Security Scan
Our scanner analyzes every file for the vulnerability patterns that Cursor's AI commonly introduces, including auth logic, data access, and secret management.
Get Fix Suggestions
Receive a prioritized report with severity ratings and concrete code fixes you can apply immediately, no security expertise needed.
Frequently Asked Questions
67% of Cursor Apps Have Critical Vulnerabilities. Is Yours One of Them?
Paste your GitHub URL. 2 minutes. Plain-English report — no security background needed. Find out if yours is cooked before your users do.
Scan My Cursor App FreeNo credit card required. See all plans