HTTP Security bug $Preferences.nsf?

How can one control security access to $Preferences.nsf db? This appears to be a virtual file. Seems like just anyone can change settings there and those changes then apply to other users from what I see. NOT GOOD!

Try it out on your server running http.

http://hostname/$Preferences.nsf?OpenPreferences&Argument

IBM any feedback or atleast a clarification?

Subject: $Preferences just sets a cookie

you are not editing any sort of server resource.

Subject: Thanks for the info. glad it is not a bug of some sorts