Flask Debug Mode Enabled

HIGH

Flask debug mode enabled. Never use debug=True in production. Use a production WSGI server like Gunicorn.

Rule Information

Language
Python
Category
Flask
Author
Code Pathfinder
Last Updated
2026-01-17
Tags
pythonflaskdebug-modeconfigurationinformation-disclosureowasp-a05cwe-489productionwerkzeugsecuritymisconfiguration
CWE References
CWE-489
CVE References
CVE-2015-5306

Interactive Playground

Experiment with the vulnerable code and security rule below. Edit the code to see how the rule detects different vulnerability patterns.

pathfinder ci --ruleset python/PYTHON-FLASK-001 --project .
Vulnerable Code
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Security Rule

Frequently Asked Questions

Common questions about Flask Debug Mode Enabled

Flask debug mode enabled. Never use debug=True in production. Use a production WSGI server like Gunicorn.
This vulnerability is rated as HIGH severity, which means it should be addressed promptly as it poses significant security risks that could lead to unauthorized access, data leaks, or system compromise.

Use Code Pathfinder to scan your Python codebase and automatically detect instances of this vulnerability pattern. Install Code Pathfinder and run the following command in your project directory:

pathfinder ci --ruleset python/PYTHON-FLASK-001 --project .

This rule is aligned with industry-standard security frameworks and classifications:

  • CWE (Common Weakness Enumeration): CWE-489
  • CVE (Common Vulnerabilities and Exposures): CVE-2015-5306
  • Tags: python, flask, debug-mode, configuration, information-disclosure, owasp-a05, cwe-489, production, werkzeug, security, misconfiguration
Yes! Code Pathfinder allows you to customize rules to match your specific security requirements and coding standards. You can modify the detection patterns, adjust severity levels, add custom sanitizers, and configure the rule to fit your organization's security policies. The interactive playground above lets you experiment with the rule and see how it behaves with different code patterns.
When this vulnerability is detected in your code, review the flagged instances carefully. Check the "Vulnerable Code" section above for examples of insecure patterns and the "Security Rule" section to understand what the rule is looking for. Follow security best practices for Python and consult the CWE/CVE references for detailed remediation guidance. Always test your fixes thoroughly before deploying to production.
Back to FlaskAll Languages →