OnnxOCR's browser WebUI renders table-recognition HTML returned by /table_api directly with innerHTML. The table HTML is assembled from OCR-recognized cell text without escaping those cell values first. A crafted image containing table cell text that is recognized as HTML-like markup can therefore be reflected into the WebUI DOM as executable HTML/JavaScript in the OnnxOCR origin.
This is a WebUI/client-side issue. I am not claiming direct unauthenticated server-side RCE from this path alone. The risk is most relevant when an operator uses the WebUI to process attacker-supplied table images, or when another workflow renders the html field returned by /table_api with the same trust assumption.
Reviewed commit: 23b9798c261ea0a23ccf6823f1bf692e4bd4e98c