Hi,
That is a very old issue, and had been properly resolved years ago. There is nothing more we can or should do about it. The issue was presented to us by security company, then registered as it should, and released after an update was already released.
It looks like wpsec uses an outdated database, or have not marked this issue as resolved correctly. If you check the wpvulndb (their source), it is marked as resolved as well: https://wpvulndb.com/vulnerabilities/7859
You can present this URL for the proof of concept and resolution.