Skip to content

Feature Request: Multi-Page Flow Support for Evil Portal #12

@Michel666-def

Description

@Michel666-def

Summary:
Enable Evil Portal to handle multi-page HTML flows, where one page redirects to another after form submission (e.g., page1 → page2 → page3), while maintaining the ability to parse and log data from each page via the same Flask backend.

Use case examples:

  • WiFi Registration Flow: Collect name → confirm via SMS → show thank-you screen.

  • Local game: Step-by-step interaction where each screen collects part of user input.

  • Legal forms: Collect personal details across multiple pages in a natural UX.

Requirements:

  1. Allow multiple HTML files per portal in /www/portals/XYZ/.

  2. Data from each form page is forwarded to Flask endpoint /api/username (or /api/log).

  3. Every POST is logged separately (invoer.txt, codes.txt, etc.).

  4. Easy switching between portal sets (e.g., /portals/gamename1/, /portals/hotel_wifi/).

  5. Works with current evil_portal.py and supports Telegram/webhook forwarding.

  6. (Optional) Enable .fab commands to activate a full portal folder with all pages.

Why this matters:
This makes Evil Portal suitable for realistic, multi-step flows without hardcoding or replacing HTMLs manually, which helps in development, testing, education, awareness, and security auditing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions