flask-werkzeug-attack

Detect exposed Flask/Werkzeug debuggers and assess remote code execution potential.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill flask-werkzeug-attack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flask-werkzeug-attack
Source: https://github.com/uphiago/recon-skills/tree/main/recon/flask-werkzeug-attack
Command: npx skills add https://github.com/uphiago/recon-skills --skill flask-werkzeug-attack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of identifying and exploiting exposed Flask/Werkzeug debuggers in production web applications, which leak sensitive server information and can enable unauthenticated remote code execution when misconfigured.

Core Features & Use Cases

  • Debugger Detection: Identify active Werkzeug debuggers via distinctive error page signatures, SECRET value disclosures, and console mode flags.
  • Sensitive Data Extraction: Pull filesystem paths, source code snippets, framework versions, and debug SECRETs from exposed traceback pages.
  • RCE Assessment: Validate if the debugger console is enabled to execute arbitrary Python commands for full server compromise. Use Case: During a June 2026 penetration test of a health SaaS platform, this Skill was used to identify an exposed debugger on port 8084, extract the server SECRET, and confirm the console was disabled to avoid false RCE assumptions.

Quick Start

Use the flask-werkzeug-attack skill to scan the target host on port 8084 for exposed Werkzeug debuggers, extract any leaked SECRET values, and check if remote code execution via the debugger console is possible.

Frequently Asked Questions about flask-werkzeug-attack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I exploit an exposed Werkzeug debugger in a Flask application?

To exploit an exposed Werkzeug debugger, identify active debuggers via error page signatures, extract sensitive filesystem paths and source code from tracebacks, and leverage enabled console modes for remote code execution.

How does a Werkzeug debugger console enable remote code execution?

The Werkzeug debugger console enables remote code execution by allowing arbitrary Python commands to run directly on the server if the console is active and the attacker validates access using exposed SECRET values.

What sensitive data can be extracted from a Flask debug traceback page?

A Flask debug traceback page can leak sensitive server data including filesystem paths, source code snippets, framework versions, and the Werkzeug debug SECRET needed for console authentication.

Can I safely assess Werkzeug RCE potential without crashing the production server?

Yes, you can safely assess Werkzeug RCE potential by detecting debugger presence through error page signatures and validating console access conditions with exposed SECRETs to avoid triggering unnecessary server errors.

How to detect if a Flask Werkzeug debugger is active on a specific port?

Detect an active Flask Werkzeug debugger on a specific port by scanning the target host for distinctive error page signatures, SECRET value disclosures, and console mode flags indicating a misconfigured production environment.