React Router version 7.0.0 marks a significant shift from the previous stable version, 6.30.1, introducing notable changes that developers should be aware of. One of the primary differences lies in the dependencies. Version 7.0.0 incorporates dependencies like cookie, turbo-stream, @types/cookie, and set-cookie-parser, suggesting enhancements related to cookie handling and potentially real-time data streaming, features absent in version 6.30.1 which relied solely on @remix-run/router.
The development dependencies also signal a transformation. Version 7.0.0 includes tools like tsup, rimraf, wireit, and particularly typescript and @types/set-cookie-parser, indicating a move towards a more robust build process, and hinting at usage of typescript for development while version 6.30.1 has react-router-dom as a dev dependency.
Furthermore, the peer dependency specifications have evolved. Version 7.0.0 mandates react and react-dom versions of at least 18, aligning with the latest React ecosystem standards, while version 6.30.1 supported React versions as early as 16.8. This suggests that upgrading to version 7.0.0 necessitates ensuring compatibility with React 18 or higher.
Finally, the dist metadata reveals a substantial increase in the package size and file count in version 7.0.0, indicating a more feature-rich or complex implementation compared to the leaner distribution of version 6.30.1. Be mindful of the release dates as there seems to be a mistake with version 7 being released the 22th of November of 2024 and version 6 being released the 20th of May of 2025.
All the vulnerabilities related to the version 7.0.0 of the package
React Router allows pre-render data spoofing on React-Router framework mode
After some research, it turns out that it's possible to modify pre-rendered data by adding a header to the request. This allows to completely spoof its contents and modify all the values of the data object passed to the HTML. Latest versions are impacted.
The vulnerable header is X-React-Router-Prerender-Data, a specific JSON object must be passed to it in order for the spoofing to be successful as we will see shortly. Here is the vulnerable code :
To use the header, React-router must be used in Framework mode, and for the attack to be possible the target page must use a loader.
Versions used for our PoC:
routes/ssr).data. In our case the page is called /ssr:We access it by adding the suffix .data and retrieve the data object, needed for the header:
X-React-Router-Prerender-Data header with the previously retrieved object as its value. You can change any value of your data object (do not touch the other values, the latter being necessary for the object to be processed correctly and not throw an error):As you can see, all values have been changed/overwritten by the values provided via the header.
The impact is significant, if a cache system is in place, it is possible to poison a response in which all of the data transmitted via a loader would be altered by an attacker allowing him to take control of the content of the page and modify it as he wishes via a cache-poisoning attack. This can lead to several types of attacks including potential stored XSS depending on the context in which the data is injected and/or how the data is used on the client-side.