Shell script execution using "basedir" as argument has problems in Windows

When using the exec-maven-plugin within a pom.xml to run a bash script located in the basedir (Windows) as follows:

<configuration>
     <executable>bash</executable>
     <arguments>
         <argument>${basedir}/scripts/script.sh</argument>
         <argument>${version}</argument>
     </arguments>
</configuration>

the parsed path when the plugin executes seems to be incorrect, the entire basedir appears without slashes, as follows:

C:UsersUsernameWhateverDirectories/scripts/script.sh

When it should be like

C:Users/Username/Whatever/Directories/scripts/script.sh

This is something that happens also for other people, so seems to be a bug in the plugin for Windows systems.
I would say this has something to be with the parsing of the escaped values (\) in the plugin itself, but I didn't go further on this investigation.

The rest of plugins and values that use the ${basedir} parameter work totally fine.
In Linux/Mac systems there's no problems.

Reproduce the exec-maven-plugin configuration from the issue on Windows with bash and scripts/script.sh, using ${basedir} as the argument. Trace how the pom.xml argument path is parsed and compare it with Linux or macOS behavior; done means the basedir path retains its separators when the script executes on Windows.