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
cve-2025-55182-lab — Intentionally vulnerable Next.js RSC Docker lab for CVE-2025-55182 (React2Shell) local testing | Kitploit
Tools/GitHubGitHub/l0lsec/cve-2025-55182-lab
Vulnerability AnalysisWeb Application ExploitationWeb SecurityPenetration TestingLearning & EducationLabs & Practice
GitHubl0lsec/cve-2025-55182-lab

cve-2025-55182-lab

Intentionally vulnerable Next.js RSC Docker lab for CVE-2025-55182 (React2Shell) local testing

View Repository
145 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

CVE-2025-55182 RSC lab (intentionally vulnerable)

Local Docker lab for authorized security research: React Server Components / Next.js App Router with a stack in the CVE-2025-55182 (React2Shell) affected range.

Use only on your own machine. Do not expose this container to the internet.

References

  • React — Critical security vulnerability in React Server Components
  • NVD — CVE-2025-55182
  • Next.js security advisories (upgrade paths for your release line)

What this runs

ComponentVersionNote
Next.js15.1.0Pre-patch; npm warns about known issues
React / react-dom19.2.0In the affected 19.x line for this CVE
RSC pipelineBundled in NextDeserialization is exercised via Next’s compiled react-server-dom-*

The app is a minimal App Router page with one Server Action so POST / with a Next-Action header behaves like a real target.

Prerequisites

  • Docker and Docker Compose v2
  • Docker engine running (e.g. Docker Desktop)

Quick start

root@kitploit:~
git clone https://github.com/l0lsec/cve-2025-55182-lab.git
cd cve-2025-55182-lab

# Build and run in the background
docker compose up --build -d

Open http://localhost:3000 — you should see “RSC lab (intentionally vulnerable)” and a small form.

Verify it is up

root@kitploit:~
curl -sS -o /dev/null -w "%{http_code}\n" http://127.0.0.1:3000/
# expect: 200

Logs

root@kitploit:~
docker compose logs -f

Stop

root@kitploit:~
docker compose down

Testing with Burp Suite

  1. Set Target to http://localhost:3000 (or tunnel through Burp).
  2. Send POST / with Content-Type: multipart/form-data and your Flight-protocol exploit body (multipart fields 0, 1, 2 as in public write-ups / your templates).
  3. Next-Action header
    • Try intercepting a normal form submit and copy the real Next-Action value from that request, or
    • Inspect the page HTML: the action id appears in hidden fields / RSC payload (it can change when you rebuild the image).

Example header shape:

root@kitploit:~
Next-Action: <action-id-from-intercepted-request>

If a generic placeholder does not work, always prefer the live id from Proxy history after one legitimate submit.

Sample raw requests

Ready-to-paste POST / multipart templates live in burp-payloads/ (e.g. id, whoami, time-based sleep, OOB placeholders). See burp-payloads/README.md for a file index. Replace YOUR-COLLABORATOR-HOST in OOB templates before sending.

Project layout

root@kitploit:~
.
├── Dockerfile              # Multi-stage build, Next standalone, port 3000
├── docker-compose.yml      # Maps host 3000 → container 3000
├── burp-payloads/          # Raw *.http for Burp Repeater + index README
├── app/
│   ├── layout.tsx
│   └── page.tsx            # Server Action + lab UI
├── public/
├── package.json
├── package-lock.json
└── next.config.ts          # output: "standalone"

Development (without Docker)

root@kitploit:~
npm install
npm run dev
# http://localhost:3000

For CVE reproduction, prefer the Docker image so the stack matches the pinned vulnerable dependencies.

After you are done testing

  • Destroy the container and image if you no longer need them.
  • Upgrade any real apps to patched Next.js / React per vendor guidance — this repo is not a secure baseline.

License

Educational / lab use only. You are responsible for complying with laws and policies where you operate. No warranty.

Download Tool