As far as I remember, the "DLL hijacking" is a serious issue when the program like Microsoft Word searches for the DLL exactly at the location of the user file

As far as I remember, the "DLL hijacking" is a serious issue when the program like Microsoft Word searches for the DLL exactly at the location of the user file to be opened and exactly after the user selects the file: if you e.g. open a .DOC file from the Documents folder and an attacker placed in the Documents folder his own DLL, that DLL would have been then loaded too by some unpatched versions of Microsoft Word. I don't see such a scenario described in this article, so it can be that the issue here has much less potential to be misused? There is also a system-wide solution for all programs at once: SafeDllSearchMode registry entry. https://www.fortinet.com/blog/industry-trends/a-crash-course-in-dll-hijacking.html https://www.fortinet.com/blog/industry-trends/a-crash-course...