// vulnerability spotlight
Every check FixVibe runs,
explained.
69+ vulnerability classes that ship with FixVibe. Each entry runs up to 35 sub-checks per scan and breaks down how the bug works, what an attacker gets out of it, how we test for it, and what it takes to defend.
01 / 07
HTTP & Surface
Session Cookie Attributes
HttpOnly, Secure, SameSite — three flags that turn a session cookie into something attackers can't easily steal.
Read the spotlight →
HTTP Security Headers
Headers are free defense — most apps still ship without them.
Read the spotlight →
TLS Configuration
Old cipher suites plus missing HSTS equals a hostile WiFi away from session hijack.
Read the spotlight →
Vercel Deployment Protection
Generated deployment URLs should not become public staging doors.
Read the spotlight →
02 / 07
Secrets
Hard-coded Secret Patterns
Stripe keys, AWS credentials, OpenAI tokens — pattern matching catches the easy mistakes.
Read the spotlight →
Secrets in JavaScript Bundles
If it shipped in your client bundle, it's not a secret — it's a publication.
Read the spotlight →
JWT Integrity (alg confusion, weak secrets)
If your JWT verifier trusts the token's own header, it will believe whatever the attacker types.
Read the spotlight →
Tokens in Browser Storage
localStorage is JavaScript-readable. Auth tokens stored there are XSS-stealable by design.
Read the spotlight →
Exposed Source Maps
If your .map files are public, the attacker is reading your TypeScript.
Read the spotlight →
Information Leakage in JavaScript
Internal API hosts, version banners, and TODO comments — small leaks add up to a map of your stack.
Read the spotlight →
03 / 07
Backend-as-a-Service
Firebase Security Rules
`allow read, write: if true` is somebody's production database right now.
Read the spotlight →
Supabase Row-Level Security
Without RLS on every public table, your anon key is a license to read anything.
Read the spotlight →
Clerk & Auth0 Configuration
Identity providers leak more than they should when defaults aren't tightened.
Read the spotlight →
Supabase Storage and API Posture
Public buckets and anon-listable objects are where BaaS data leaks start.
Read the spotlight →
04 / 07
DNS
05 / 07
Discovery
CVE Cross-Reference
Detected version + public CVE database = a list of attacks already documented.
Read the spotlight →
Debug & Admin Endpoints
/debug, /admin, /server-status — paths that should never be reachable from the internet.
Read the spotlight →
Exposed Files & Backup Directories
.env, .git, .DS_Store, backup.sql — files that should never be public, accidentally are.
Read the spotlight →
SPIP Template RCE Version Exposure
Public SPIP version banners can reveal an RCE-class patch gap.
Read the spotlight →
Cloudflare Origin & Proxy Posture
If your origin IP is discoverable, Cloudflare's WAF is bypassable.
Read the spotlight →
GraphQL Introspection Exposed
Introspection in production hands the attacker your full type system.
Read the spotlight →
Threat-Intel Cross-Reference
Spamhaus DBL, URLhaus — your domain's reputation, externally seen.
Read the spotlight →
Exposed API Documentation
/swagger.json, /openapi.json, /docs — public API maps for both you and the attacker.
Read the spotlight →
Netlify-Specific Exposure
Netlify deploy preview URLs, x-nf-* headers, _redirects mistakes.
Read the spotlight →
Privacy & Cookie Compliance Markers
GDPR-required pages — present and linked, or you're at risk of a complaint.
Read the spotlight →
Technology Fingerprinting
Knowing your stack is half the recon — outdated frameworks turn that into the other half.
Read the spotlight →
Vercel-Specific Exposure
_next/static, x-vercel-* headers, preview URLs — Vercel-isms that leak more than they should.
Read the spotlight →
06 / 07
Aktywne sondy
Cross-Tenant Data Leaks
Multi-tenant SaaS without tenant ID enforcement leaks customer data across orgs.
Read the spotlight →
JWT alg=none Acceptance
A decoded token is not an authenticated identity.
Read the spotlight →
OS Command Injection
When user input becomes part of a shell command, the shell runs whatever the attacker writes.
Read the spotlight →
Server-Side Template Injection (SSTI)
When a template engine treats user input as a template, the server treats user input as code.
Read the spotlight →
SQL Injection
When user input becomes part of a query, the database stops being yours.
Read the spotlight →
Auth Flow Defects
Login, signup, and password reset are where most account takeovers actually happen.
Read the spotlight →
Blind SSRF (Out-of-Band)
If the server fetches user-supplied URLs, the user can make it fetch internal services.
Read the spotlight →
CKAN DataStore SQL Authorization Bypass
Public DataStore SQL access can turn open data APIs into private data exposure.
Read the spotlight →
CORS Misconfiguration
Permissive Access-Control-Allow-Origin plus credentials means your API is everyone's API.
Read the spotlight →
DOM-based XSS via URL Fragment
Modern SPAs read location.hash and write it into the DOM — attacker payloads ride along.
Read the spotlight →
File Upload Validation
User-uploaded files are arbitrary bytes — accepting them as 'images' without checking is asking for RCE.
Read the spotlight →
FUXA Hardcoded JWT Fallback Secret
Default token-signing secrets can turn an HMI login into a weak boundary.
Read the spotlight →
GraphQL Depth Bombing & Batch Bypass
GraphQL's flexibility is also its vulnerability — depth bombs, alias batching, and field-suggestion leaks.
Read the spotlight →
HTTP Request Smuggling
Front-end proxy and back-end disagree on where one request ends — attacker rides the seam.
Read the spotlight →
IDOR / BOLA
If your API trusts the client to send the correct ID, the client can send any ID.
Read the spotlight →
LLM Prompt Injection
If your AI feature trusts user input as instruction, the user can rewrite the system prompt.
Read the spotlight →
NoSQL Operator Injection
MongoDB-style operators in user-controlled JSON turn your query into a wildcard.
Read the spotlight →
Reflected Cross-Site Scripting (XSS)
The silent hijack: when a single unsanitized parameter executes attacker code in your users' browsers.
Read the spotlight →
XML External Entity (XXE)
If your XML parser resolves external entities, your server reads files for the attacker.
Read the spotlight →
ZoneMinder Directory Listing Exposure
A camera management UI should not publish its web root index.
Read the spotlight →
Account Enumeration
If your login responds differently when the email exists vs doesn't, attackers can build a customer list.
Read the spotlight →
Confirming Next.js middleware bypass exposure
Confirming Next.js middleware bypass exposure
Read the spotlight →
CRLF / Response Splitting
If user input lands in a response header, line breaks let the attacker write their own headers.
Read the spotlight →
CSRF Protection
If your state-changing endpoints don't require a CSRF token, third-party sites can act as your users.
Read the spotlight →
Missing Rate Limiting
Without rate limits on auth endpoints, the attacker can credential-stuff at line speed.
Read the spotlight →
Next.js Header Configuration Drift
Headers set on `/` do not always protect nested routes.
Read the spotlight →
Open Redirect
Your /redirect?url=… that doesn't validate the destination is a phishing kit.
Read the spotlight →
07 / 07
Source code
Ghost Content API SQL Injection Advisory
A vulnerable Ghost dependency can put public content APIs on the database boundary.
Read the spotlight →
LibreNMS Command Injection Advisory
A vulnerable monitoring stack can become an execution path inside the network.
Read the spotlight →
LiteLLM SQL Injection Advisory
A vulnerable LiteLLM Proxy version can turn API-key verification into database exposure.
Read the spotlight →
Committed AI-Generated Secrets
AI snippets should not ship provider keys into git.
Read the spotlight →
electerm Install-Script Command Injection Advisory
A vulnerable terminal-client dependency can put build or developer hosts at install-time risk.
Read the spotlight →
OpenCms XXE Information-Disclosure Advisory
A vulnerable OpenCms dependency can put XML-processing routes on a file-read boundary.
Read the spotlight →
PDF.js JavaScript Execution Advisory
A vulnerable PDF viewer can turn a malicious document into script execution.
Read the spotlight →
Risky Source-Code Patterns
eval(), dangerouslySetInnerHTML, hard-coded secrets — the patterns SAST has been catching for 25 years.
Read the spotlight →
Supabase RLS in Migrations
A public table without RLS is a future data leak.
Read the spotlight →
Vulnerable Dependencies
Your package-lock.json includes thousands of packages. Some have known CVEs.
Read the spotlight →
Webhook Signature Verification
If your webhook handler doesn't verify the signature, anyone can forge events.
Read the spotlight →
AI-Generated Code Guardrails
Fast AI-assisted changes need repo-level security rails.
Read the spotlight →
Repo Security Hygiene
Branch protection, action pinning, secret hygiene — how your repo is run matters more than the code.
Read the spotlight →
Reviewing repo code against web app risk patterns
Reviewing repo code against web app risk patterns
Read the spotlight →