Is this still a vunerability in Fiesty?
Shouldn't Fiesty merge to the upstream version 4.1.2 which doesn't have the problem? Its very confusing to tell if vunerable or not if fixes are backported, but the version number is still based at the known broken 4.1.1.
Is this still a vunerability in Fiesty?
Shouldn't Fiesty merge to the upstream version 4.1.2 which doesn't have the problem? Its very confusing to tell if vunerable or not if fixes are backported, but the version number is still based at the known broken 4.1.1.