ToolJet Security Issues
The most common security gaps in ToolJet applications — and how to fix them before they become an incident.
Results in minutes. From $9.
4 Security Issues Documented
Common vulnerabilities found in ToolJet applications
High Severity Issues
Unparameterized AI Queries
highToolJet 3.0's AI Query Builder generates SQL from natural language. These queries may not use parameterized inputs, creating injection vectors.
Session hijacking, data theft, and arbitrary actions executed on behalf of logged-in users. XSS also enables keylogging and credential phishing within your own domain.
Submit test payloads (`<script>alert(1)</script>`, `' OR 1=1 --`) through every user input field. Any reflection or query error confirms the issue.
Use parameterized queries, sanitize all user input, and render dynamic content with framework escaping (React JSX, not dangerouslySetInnerHTML).
Exposed Data Source Credentials
highDatabase passwords and API keys may be accessible to all workspace members or exposed through misconfigurations.
Third-party API abuse (OpenAI quota drained, Stripe charges made), lateral access to connected services, and disclosure of internal systems.
Open the deployed app in a browser, view-source on the main bundle, grep for patterns like `sk-`, `sk_live_`, `eyJ`, `AKIA`, `AIza`. A single match is a confirmed exposure.
Move all secrets server-side (environment variables, serverless functions). Rotate any keys previously in frontend code. Audit bundles for leftover credentials before each deploy.
Admin Panel Without Auth
highSelf-hosted ToolJet instances may expose the admin interface without proper authentication or IP restrictions.
Account takeover of legitimate users. Attackers gain full access to victim accounts and any data/actions those accounts permit.
Attempt 20+ login requests with the same username in under 60 seconds. If all complete without rate limiting or lockout, the issue is present.
Enforce email verification, minimum password requirements, and rate limiting on auth endpoints. Test auth flows as unauthenticated and cross-user to verify access controls.
Medium Severity Issues
Overly Permissive Query Access
mediumUsers may be able to execute any query against connected data sources, not just the queries their role requires.
Attack surface expansion. In combination with other findings, enables data exposure, account compromise, or service abuse.
Run a VAS scan against the deployed ToolJet app URL — automated detection is the fastest and most reliable path.
Scan your deployed application with a security tool that understands this stack. Address the specific findings — generic best practices don't catch platform-specific misconfigurations.
How to Prevent These Issues
- Run automated security scans before every deployment
- Configure database access controls (RLS/Security Rules) first
- Store all secrets in environment variables, never in code
- Enable email verification and strong password policies
- Add security headers to your hosting configuration
- Review AI-generated code for security before accepting
Find Issues Before Attackers Do
VAS scans your ToolJet app for all these issues automatically. Scans from $9, instant results.
Get Starter ScanFrequently Asked Questions
What are the most common ToolJet security issues?
The most common issues are: exposed API keys/secrets, missing database access controls (RLS or Security Rules), weak authentication configuration, and missing security headers. These account for over 80% of vulnerabilities in ToolJet applications.
How do I find security issues in my ToolJet app?
Run a VAS security scan for automated detection of common vulnerabilities. Manually check: database access controls, search code for hardcoded secrets, verify authentication settings, and test security headers. VAS catches all of these automatically.
Are ToolJet security issues fixable?
Yes, nearly all ToolJet security issues are configuration problems with straightforward fixes. Missing RLS, exposed secrets, weak auth—all have clear remediation steps. Most fixes take under an hour to implement.
How quickly can ToolJet security issues be exploited?
Exposed databases and API keys can be discovered within minutes using automated scanners. Attackers actively scan for common patterns. This is why security configuration must happen before deployment, not after.
Does ToolJet have built-in security?
ToolJet provides security features, but they require configuration. Security isn't automatic—you must enable database access controls, manage secrets properly, configure auth settings, and add security headers. The tools exist; you must use them.
Related ToolJet Security Resources
Similar Platforms
More on ToolJet Security
Every angle of ToolJet security — from the specific findings we detect to step-by-step fixes.
ToolJet Security Scanner
Hub page: scan your ToolJet app for vulnerabilities.
ToolJet Security Risks
Specific risks we find in ToolJet apps, with real-world examples.
ToolJet Best Practices
Remediation playbook derived from ToolJet's actual failure modes.
ToolJet Security Checklist
Pre-launch checklist covering every finding class for ToolJet.
How to Secure ToolJet Apps
Step-by-step hardening guide for ToolJet deployments.
Last updated: April 20, 2026