The issue allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks. This is achieved via a Trojan horse `ibfs32.dll` located in the same folder as certain file types, including `.indl`, `.indp`, `.indt`, or `.inx` files.