React Router DOM is a popular library for declarative routing in React web applications, enabling developers to build single-page applications with smooth navigation and dynamic content rendering. Comparing versions 7.1.4 and 7.1.3, several key aspects stand out for developers considering upgrading. Both versions share the same fundamental dependencies, including a core reliance on react-router (with matching version numbers, suggesting synchronized core functionality), and identical development dependencies like tsup, react, react-dom, typescript, and wireit, which implies a consistent development and build process. The peer dependencies also remain constant, requiring react and react-dom versions of 18 or greater, ensuring compatibility with modern React projects.
The most apparent difference lies in the release dates. Version 7.1.4 was released on "2025-01-30T16:22:15.553Z", while version 7.1.3 came out on "2025-01-17T21:55:40.009Z". This two weeks gap suggests that 7.1.4 might incorporate bug fixes, performance improvements or minor feature enhancements over 7.1.3. Developers should check official release notes or changelogs for the detailed list (if available). Other aspects like description, license, repository URL, author and the number and size of archive contents appear to be the same, potentially indicating that the core architecture and distribution method remained unchanged between these minor version updates. Developers should always prioritize reviewing comprehensive changelogs or upgrade guides when migrating between versions to address any potential breaking changes or newly introduced features.
All the vulnerabilities related to the version 7.1.4 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.