TL;DR; see answer with stackoverflow for simple worksheet protection
depending on the kind of protection (workbook, sheet, on open and so on) and excel version used, there is/was a macro out there for bruteforcing simple passes if you are able to open the excel-file normally and have access to the VBA developer options (alt+f11) google is your friend
but be aware im quite sure, that the last excelversion for "attacking" is Excel 2010 as afterwards these vba attack was blocked internally by microsoft, so you have to open the file with an older version of excel for running the attack
but never the less, please also see this answer by Alexander Don'valderath, when its just plain sheet protection, its enough to delete the corresponding XML node inside the worksheet, this answer still works even on LTS Office 2016
https://stackoverflow.com/questions/1995...d-with-vba
depending on the kind of protection (workbook, sheet, on open and so on) and excel version used, there is/was a macro out there for bruteforcing simple passes if you are able to open the excel-file normally and have access to the VBA developer options (alt+f11) google is your friend
but be aware im quite sure, that the last excelversion for "attacking" is Excel 2010 as afterwards these vba attack was blocked internally by microsoft, so you have to open the file with an older version of excel for running the attack
but never the less, please also see this answer by Alexander Don'valderath, when its just plain sheet protection, its enough to delete the corresponding XML node inside the worksheet, this answer still works even on LTS Office 2016
https://stackoverflow.com/questions/1995...d-with-vba