Scanner Tool for Detecting Critical "React2Shell" RCE Vulnerabilities in React and Next.js

This GitHub repository contains a comprehensive scanning toolset designed to detect and remediate two critical, unauthenticated remote code execution (RCE) vulnerabilities—CVE-2025-55182 (React) and CVE-2025-66478 (Next.js)—both rated CVSS 10.0. Dubbed "React2Shell," this flaw in the React Server Components (RSC) Flight protocol allows a single crafted HTTP request to deserialize into server-side code execution on vulnerable systems. The project provides two primary tools: a Software Composition Analysis (SCA) scanner to identify vulnerable dependencies in a codebase, and a web Dynamic Application Security Testing (DAST) scanner to actively probe live endpoints and validate exploitability in production environments. The web scanner includes a full test lab with exploit examples and is capable of scanning targets at scale, generating multiple report formats, and correlating findings with known attack patterns. The repository emphasizes that this is a critical security incident requiring immediate patching, scanning for vulnerable versions, and auditing logs for potential compromise. 

https://github.com/Security-Phoenix-demo/react2shell-scanner-rce-react-next-CVE-2025-55182-CVE-2025-66478

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

Secure Vibe Coding Guide: Best Practices for Writing Secure Code

Ken Huang's "Secure Vibe Coding Guide" emphasizes the importance of integrating security into the software development lifecycle. The guide provides best practices for writing secure code, including input validation, proper authentication mechanisms, and secure data storage techniques. It also highlights the necessity of regular code reviews and staying updated with the latest security vulnerabilities and patches. By following these guidelines, developers can create applications that are resilient against common security threats and contribute to a safer digital environment.  https://kenhuangus.substack.com/p/secure-vibe-coding-guide
Read more

KEVIntel: Real-Time Intelligence on Exploited Vulnerabilities

KEVIntel is a dynamic platform providing up-to-date information on known exploited vulnerabilities (KEVs). It aggregates data from over 50 public sources, including CISA, and enriches each entry with metadata such as EPSS scores, online mentions, scanner inclusion, and exploitation status. The platform aims to serve as an early warning system, offering insights even before official publications. KEVIntel supports various formats like JSON, CSV, and RSS, facilitating integration into security operations. These entries include CVSS scores, exploit status, and links to proof-of-concept code, aiding organizations in prioritizing remediation efforts.   https://kevintel.com/
Read more