React Router has released version 7.1.5, a minor update following version 7.1.4. Both versions maintain the core functionality of providing declarative routing for React applications, ensuring seamless navigation and dynamic content rendering. The dependency structure remains consistent, with essential dependencies like cookie, turbo-stream, @types/cookie, and set-cookie-parser staying at the same versions. Similarly, development dependencies for building and testing, including tsup, react, react-dom, typescript, rimraf, wireit, and @types/set-cookie-parser, are unchanged allowing a smooth transition for contributors.
Peer dependencies also stay the same, requiring React and React DOM versions to be >=18, thus minimizing breaking changes and maximizing adoption. The license, repository, and author information are identical, confirming the project's stability and continued maintainership by Remix Software. The key difference lies in the dist object: version 7.1.5 shows a slightly increased unpacked size (2281238 bytes compared to 2280964 bytes in 7.1.4), suggesting minor code additions, improvements, or bug fixes. Furthermore, the releaseDate indicates that version 7.1.5 was published on "2025-01-31", 1 day after than version 7.1.4 which was published on "2025-01-30". Developers upgrading should review the changelog for specific fixes and enhancements included in this version, but can anticipate seamless upgrade since only minor changes or bug fixes were added, thus enhancing overall performance without affecting code structure.
All the vulnerabilities related to the version 7.1.5 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.