React Router DOM versions 7.1.3 and 7.1.2 offer declarative routing solutions for React web applications, facilitating navigation and dynamic content rendering. The core functionality remains consistent between the two, as reflected in their shared description and dependency on corresponding versions of the react-router package (7.1.3 and 7.1.2 respectively). Both require React and React DOM versions 18 or higher, ensuring compatibility with modern React development practices. The packages utilize similar build and development tools, including tsup for bundling, wireit for managing scripts, and TypeScript for type safety.
Key differences lie primarily in their release dates and potentially associated bug fixes or minor improvements within the routing logic. Version 7.1.3 was released on January 17, 2025, while version 7.1.2 was released a day earlier, on January 16, 2025. Developers should consider upgrading to the newer version (7.1.3) to benefit from the latest refinements and stability enhancements. The unpacked size and the file count are identical. By upgrading your packages you are reducing the risk of facing issues that have already been handled.
All the vulnerabilities related to the version 7.1.3 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.