I can confirm this problem exists on a recent Windows version of Wireshark.
This issue happens when one right clicks on the web traffic content column and use it as filter. If the content contains double quotes, it will not be escaped, leading into syntax error and possible command injection vulnerabilities.