The vulnerability stems from two primary mechanisms: 1) The bucket storage system allows unrestricted HTML file uploads and serves them with executable context. 2) The display rendering system processes untrusted OPI files containing JavaScript references. Both mechanisms lack proper input validation and output encoding. The functions are inferred from the described attack vectors (HTML file upload/execution and display file JS injection) and typical Yamcs architecture patterns, though exact method names aren't visible in available sources. The high confidence comes from the vulnerability's technical description matching these common web service patterns and the CWE-79 classification.