Skip to main content
CriticalContentOWASP A07:2021CWE-798

How to fix: Database connection string in source

A database connection string containing credentials is visible in client-accessible source or configuration files.

Why it matters

An exposed database connection string gives an attacker direct access to your database, bypassing all application-level security controls and allowing them to read, modify, or delete all data.

Connection strings must be stored in environment variables or a secrets manager, never in source code or public-facing files.

How to fix it

  1. 1Immediately rotate the database credentials
  2. 2Move the connection string to an environment variable or secrets manager
  3. 3Ensure .env files are in .gitignore and not served by the web server

Code examples

Store connection strings in environment variables

JavaScript
// Unsafe: hardcoded connection string
const pool = new Pool({ connectionString: 'postgresql://user:pass@host/db' });

// Safe: read from environment
const pool = new Pool({ connectionString: process.env.DATABASE_URL });

References

Detected automatically by VulnRadar. The check id is database-connection-string, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is Database connection string in source?
VulnRadar rates this critical severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id database-connection-string, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Database connection string in source map to?
It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for database connection string in source

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Database connection string in source | VulnRadar