The Windows Scripting Host (WSH) consists of two tools, cscript.exe for command-line scripts and wscript.exe for UI scripts, and executes Visual Basic scripts (though it doesn’t care about the extension). WSH operates with regular user privileges, not admin privileges.
An example VBScript:
Executing a program requires creating a “shell” object:
It appears that recent versions of Windows may severely limit which binaries can be called from the wscript.Shell object; calc.exe works, but pretty much nothing else does.