There are current concerns around:
which is yet to have a patch made available.
I found this excellent article:
which provide some PowerShell scripts to create Word documents that can be used to test for the vulnerability.
I have run these scripts to create the actual Word documents and uploaded them for you here:
In both cases, when you open these documents, you should NOT be able to get CALC.EXE to execute on your system unlike what you see above and below.
I have also added these tests to my security testing script which you can download from my GitHub repo here:
When I opened these documents in my production environment, the vulnerability was largely blocked thanks to Windows ASR which I have detailed previously:
You can use the follow KQL query as I did above to view the result of this blocking if you are using something like Azure Sentinel like I am:
| where ActionType startswith ‘Asr’