Skip to main content
LowCodeOWASP A05:2021CWE-489

How to fix: Console Logging in Production

Extensive console.log statements detected.

Why it matters

May expose sensitive debug information.

Console logs can reveal internal state.

How to fix it

  1. 1Remove or disable console.log in production.

Code examples

Strip console.log in production builds

JavaScript
// vite.config.ts or next.config.mjs
export default {
  esbuild: {
    drop: process.env.NODE_ENV === "production" ? ["console", "debugger"] : [],
  },
};
// Or use a logger that respects log levels:
import log from "loglevel";
log.setLevel(process.env.NODE_ENV === "production" ? "warn" : "debug");
log.debug("only in dev"); // silent in production

References

Detected automatically by VulnRadar. The check id is console-log-production, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is Console Logging in Production?
VulnRadar rates this low severity in the code 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 console-log-production, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Console Logging in Production map to?
It maps to CWE-489. In the OWASP Top 10 it falls under A05: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 console logging in production

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: Console Logging in Production | VulnRadar