Vibe-Coded Applications Riddled With Exploitable Security Flaws — Theori Xint.io Study Finds 434 Issues Across AI-Generated Codebases — Threadlinqs Intelligence
As of 2026-07-22, Vibe-Coded Applications Riddled With Exploitable Security Flaws — Theori Xint.io Study Finds 434 Issues Across AI-Generated Codebases is a medium-severity threat intel threat, tracked by Threadlinqs Intelligence with 9 detection rules (Splunk SPL, Microsoft KQL, Sigma) and 22 indicators of compromise.
Threat ID: TL-2026-1622 · Severity: MEDIUM · Status: ACTIVE · Category: THREAT_INTEL
Theori's autonomous pentest platform Xint.io found 434 exploitable security issues across three AI-generated ("vibe-coded") application test scenarios — two greenfield builds and one hardened legacy
Theori, a security firm known for large-scale AI-driven code auditing (its Xint Code / Xint.io platform swept the database category at the 2025 ZeroDay Cloud competition by discovering critical RCEs in Redis, PostgreSQL, and MariaDB), ran its autonomous pentest platform against three representative 'vibe-coded' application scenarios to quantify the real-world security debt of AI-assisted development: (1) a new application built from a well-written specification with experienced developer oversight, (2) a new application built from a casual, unstructured directive with minimal oversight, and (3) Gnuboard7, a legacy PHP CMS hardened and migrated to a modern Laravel + React stack — representing the increasingly common 'AI-assisted legacy modernization' pattern. Each app received a 30-minute autonomous runtime-plus-source-code scan.
Across the three apps, Xint.io surfaced 434 exploitable issues: 196 in the two greenfield apps and 238 in the migrated brownfield Gnuboard7 app. The dominant category (93 findings) was resource exhaustion / denial-of-service stemming from missing rate-limiting controls — AI code generators reliably implement the functional request-handling path but omit throttling, backoff, and abuse controls unless explicitly prompted. The second-largest category (88 findings) was authorization and IDOR (Insecure Direct Object Reference / Broken Object-Level Authorization) — generated database queries filter strictly on the requested identifier (e.g. `SELECT * FROM orders WHERE id = :id`) without validating that the requesting principal actually owns the referenced object, letting any authenticated user enumerate or modify records belonging to others. Access-boundary issues — path traversal, SSRF, and related boundary-crossing flaws — made up 54 findings, frequently surfacing in URL-preview / file-fetch / import features where the generated code passes user-supplied URLs or paths directly into filesystem or HTTP-client calls without allowlisting internal address ranges or normalizing paths. Eleven critical-severity findings were hardcoded or default secrets (API keys, DB passwords, JWT signing secrets baked into source or config as string literals, then propagated across files via stateless code generation and persisted in git history even after later removal), and six were debug-mode remote code execution — frameworks (e.g. Django/Flask-style debug consoles, Laravel debug pages) left enabled in production-reachable configurations, exposing interactive code-execution consoles or verbose stack traces with secrets.
A structurally significant finding is that the IDOR flaw share nearly tripled — from 11% of findings in the smaller greenfield apps to 28% in the larger, more complex Gnuboard7 migration — indicating that authorization-boundary defects compound disproportionately as AI-generated/AI-assisted codebases grow in scope and object-relationship complexity, a pattern consistent with prior industry findings (e.g. a 15-app, 5-agent study reporting 100% of AI coding agents introduced SSRF via URL-preview features and 0% implemented CSRF protection; the May 2025 Lovable mass-exposure incident, CVE-2025-48757, in which 170+ vibe-coded applications had their backing databases fully exposed due to missing/misconfigured access controls; and Cloud Security Alliance research describing a broader 'AI-generated code vulnerability surge' with Fortune 50 empirical data showing AI-assisted developers commit 3-4x faster than peers while introducing security findings at 10x the rate).
Notably, traditional injection classes — SQL injection and XSS — appeared far less frequently than anticipated, which the researchers attribute to genuine improvement in foundation-model training/tooling around those specific, well-studied vulnerability classes (extensive public training data, linting, and framework-level ORM/templating defaults). The residual risk in AI-generated code has instead concentrated in *business-logic and authorization-bou
Weaknesses (CWE)
CWE-770, CWE-862, CWE-639, CWE-22, CWE-918, CWE-798, CWE-287, CWE-347, CWE-94, CWE-489
Target sectors: software-development, technology, startups, finance, health, ecommerce, government administration, education
Target regions: Global
Related threats
- Multiple JetBrains Product Vulnerabilities: Account Takeover, Privilege Escalation, and RCE Across Hub, YouTrack, IntelliJ IDEA, Kotlin, GoLand, and TeamCity
- AI-Accelerated WordPress Plugin Vulnerability Research Surfaces 16 Unreported Bugs Across Dozens of Plugins
- QNAP QSA-26-10: Multiple Injection and Memory-Safety Vulnerabilities in QTS, QuTS hero, QuTS cloud, QVP, and File Station (CVE-2025-66273, CVE-2026-26240, and 12 others)
Detections & IOCs
As of 2026-08-26, this threat has 9 detection rule(s) across Splunk SPL, Microsoft KQL and Sigma, and 22 indicator(s) of compromise. Detection query text and full IOC values are available to authenticated users and programmatically via the Threadlinqs MCP server (Purple tier). View plans.
THREAT_INTEL, MEDIUM, threat intelligence, cybersecurity, T1595.002, T1588.006, T1190, T1133, T1059, T1203, T1078, T1068, T1548, T1211
