The issue is related to an unescaped payload in exceljs, allowing a possible cross-site scripting (XSS) attack via cell value when a worksheet is displayed in a browser. This is due to exceljs not validating data from parsed XLSX files and embedding HTML tags, like <script>, directly into sheet cells, making it possible to inject malicious JavaScript code and execute it when data from the sheet is displayed in the browser.