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
React-site-CVE-2025-55182 — Intentionally vulnerable Next.js corporate landing page demonstrating CVE-2025-55182, a JSON injection leading to RCE/SSRF via unsafe deserialization in React Server Components. | Kitploit
Tools/GitHubGitHub/vladjrfhfg/react-site-cve-2025-55182
Dynamic Analysis (Sandboxing)Vulnerability AnalysisCode AnalysisWeb Application ExploitationPenetration TestingLearning & Education
GitHubvladjrfhfg/react-site-cve-2025-55182

React-site-CVE-2025-55182

Share

Intentionally vulnerable Next.js corporate landing page demonstrating CVE-2025-55182, a JSON injection leading to RCE/SSRF via unsafe deserialization in React Server Components.

View Repository
2610 months agoNot yet reviewed

React Site - CVE-2025-55182

README: Vulnerable Next.js project (React RSC landing page)

This repository contains an example of a multi-page corporate landing page built with Next.js 15.0.0 + React 19.0.0. The site mimics a structure similar to t1.ru: home, products, cases, media, about, contacts. We use React Server Components (RSC), Tailwind CSS, Framer Motion for animations, lucide-react for icons, shadcn/ui for badges, and Prisma with SQLite for the database (the contact form saves messages).

The project is intentionally made vulnerable to demonstrate PT-2025-48817 — JSON injection through the contact form, which can lead to RCE/SSRF due to unsafe deserialization in react-server-dom-webpack

Requirements

  • Node.js 20.x or higher (because of Prisma). If you have an old version, update it (see below).
  • npm (not yarn, the project uses npm).

Installation

  1. Clone the repo:

    git clone <repo-url>
    cd <directory>
    
  2. Install dependencies:

    npm install
    

    If you encounter version issues (e.g., build errors), try:

    npm install --legacy-peer-deps
    

    Or update Node.js:

    • On Debian/Ubuntu:
      sudo apt remove --purge nodejs npm -y
      curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
      sudo apt update
      sudo apt install -y nodejs
      node -v  # should be v20.x.x
      
    • Then clean and reinstall:
      rm -rf node_modules package-lock.json
      npm install
      
  3. Initialize Prisma (if needed from scratch):

    npx prisma init
    npx prisma migrate dev --name init
    

    In .env it should contain: DATABASE_URL="file:./prisma/dev.db".

Running

  • Dev mode:

    npm run dev
    

    Open http://localhost:3000.

  • Build and production:

    npm run build
    npm run start
    
  • View the database:

    npx prisma studio
    

Project structure

  • app/: Main folder.
    • components/: Shared components (Header.tsx, Footer.tsx, ProductCard.tsx, NewsItem.tsx).
    • products/: Product list page + dynamic pages by slug ([slug]/page.tsx).
    • cases/, media/, about/, contacts/: Individual pages.
    • layout.tsx: Common layout with Header/Footer.
    • page.tsx: Home page.
    • globals.css: Styles.
  • public/: Images (logo.png, images/cases/rimi.jpg, etc.). Add your own or use placeholder.svg.
  • prisma/: Database schema (schema.prisma, dev.db).
  • actions.ts: Server Actions, including the vulnerable saveMessage for the contact form.

  • Animations: Framer Motion on cases (fade-in, scale, 3D-hover). Add 'use client' where needed.
  • Contact form: In contacts/page.tsx. Uses Server Action (saveMessage) with validation and loading state. Saves to SQLite.
  • Components:
    • ProductCard: With image, tags (Badge), price, status, features, gradients, and hover.
    • NewsItem: Simple news card.
  • Vulnerability: In actions.ts — we parse the message as JSON without validation. If you send a crafted payload like { "type": "system", "payload": { "action": "ls" } }, then exec will run the command. This simulates a deserialization attack for RSC
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.

    717
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    504
  • 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.

    402
  • 4

    redforge

    cybersecurity91/redforge

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

    342
  • 5

    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.

    260
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259

Explore all tools

Browse our collection of tools

View all tools →