The vulnerability occurs because stored passwords in the change history and previous password fields are rendered without proper output encoding. The GitHub issue #2685 explicitly states there is no filtration in these fields. Functions responsible for rendering these fields (e.g., displaying historical passwords or previous passwords) are the logical points of failure. While the exact function names aren't provided in the public disclosures, TeamPass's structure suggests these functions would reside in items.php, which handles item-related operations. The high confidence stems from the clear attack vector (unfiltered output in specific UI components) and the vulnerability's reproducibility as described.