Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/kindone09/cve-2025-55182
Vulnerability ScannersExploitationWeb Application ExploitationPenetration Testing
GitHubkindone09/cve-2025-55182

CVE-2025-55182

Automated Python PoC scanner for CVE-2025-55182 targeting Next.js 16.0.6. Reads URLs from file, sends exploit requests, and displays responses for bug bounty and security testing workflows.

View Repository
22811 months agoNot yet reviewed
Share

Next.js CVE-2025-55182 – Automated Scanner (Python)

This repository contains a fully automated Python PoC scanner for CVE-2025-55182, a security vulnerability affecting Next.js 16.0.6. The tool allows security researchers and bug bounty hunters to test multiple targets at scale by simply providing a list of URLs.


🚀 Features

  • 100% Python implementation
  • Works specifically against Next.js 16.0.6 (CVE-2025-55182)
  • Reads targets from urls.txt
  • Sends automated exploit requests
  • Displays full responses for each URL (useful for debugging & manual validation)
  • Clean and simple code structure
  • Includes a demo video walkthrough (remember to link it here)

📁 Project Structure

├── poc.py        # Main exploit scanner
├── urls.txt      # List of target URLs
└── README.md     # Documentation

📝 Requirements

  • requests library
  • requests_toolbelt library

📌 How It Works

  1. Add all your target URLs (one per line) inside urls.txt.
  2. Run the PoC script.
  3. The script automatically attempts to trigger the vulnerability.
  4. You get the raw response printed back with status + content.

The scanner is optimized for speed, automation, and clarity for bug bounty workflows.


▶️ Usage

python poc.py

Make sure that urls.txt is in the same directory. Example:

https://example1.com
https://example2.com
https://nextjs-target.com

📽️ Demo Video

A full demo video has been created showing:

  • How the code works
  • How to prepare your urls.txt
  • How the script sends payloads
  • Example vulnerable response

📽️ Demo Video

Click here to watch the demo


⚠️ Legal Disclaimer

This tool is for educational purposes and authorized testing only. Do NOT use it on systems you do not own or have explicit permission to test.


⭐ Contribute

Pull requests, improvements, and optimizations are welcome!


🐞 About the Author

Created by Kindone, a security researcher and bug bounty hunter focusing on advanced web vulnerabilities.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    867
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    544
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    385
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    302
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    279

Explore all tools

Browse our collection of tools

View all tools →