A local privilege escalation vulnerability exists in Softros LAN Messenger 9.6.4, allowing attackers to execute arbitrary code via an unquoted service path.

The application contains an unquoted service path vulnerability within the SoftrosSpellChecker service. This flaw allows a local, authenticated attacker to place a malicious executable in the path hierarchy, which the system will execute with LocalSystem privileges during the service startup process.

Successful exploitation of this vulnerability allows a local attacker to escalate their privileges to the highest level on the host system. This could lead to a total compromise of the affected machine, including unauthorized access to sensitive data, the installation of persistent backdoors, and the potential for lateral movement within the network. The CVSS score of 7.8 reflects the high severity of achieving full system control via local access.

Immediate Action: Update Softros LAN Messenger to the latest available version provided by the vendor to resolve the service path configuration. If an update is not immediately available, administrators should manually modify the service path registry entry to include quotes around the executable path.

Proactive Monitoring: Review system event logs for unexpected service restarts or failures related to the SoftrosSpellChecker service. Monitor file system activity within the C:\Program Files (x86)\Softros Systems\ directory for the creation of unauthorized or suspicious executable files.

Compensating Controls: Implement strict file system permissions on the installation directory to prevent non-privileged users from creating or modifying files within the Softros Messenger path. Utilize Endpoint Detection and Response (EDR) solutions to alert on suspicious process spawning from service paths.

Public Exploit Available: Yes, a proof-of-concept exploit is available via the Exploit Database (EDB-ID: 49588).

This vulnerability presents a significant risk to local system integrity by enabling unauthorized privilege escalation. Administrators must prioritize updating the software or applying the manual registry fix to secure the service path. Failure to address this flaw leaves the host susceptible to full administrative compromise by local users.