EDIT: I misunderstood. You need write access to a config file that should only be on the local filesystem, not the kdbx. So if I'm understanding, a common usag

EDIT: I misunderstood. You need write access to a config file that should only be on the local filesystem, not the kdbx. So if I'm understanding, a common usage pattern for Keepass is keeping the kdbx on a shared drive (OneDrive, Dropbox, etc.) Someone with read/write access to a bunch of Dropbox shares could perform this exploit on a bunch of kdbx files so that it will write plaintext files to the share, then wait and collect the passwords. It would be hard to hide the attack but it would be incredibly damaging. So I'm not sure the assertion that this requires local access is correct. It sounds like it only needs access to a shared filesystem that contains a kdbx, and I think it is reasonable to expect Keepass to be secure against that.