Use distinct authkey per node operation

Created on 1 July 2011, almost 14 years ago
Updated 11 August 2023, over 1 year ago

Since the same authkey is used to grant access to node for view, edit and delete, a security hole is exposed when users with a view link can use the same authkey to perform other operations on the node.

Example :

A user with a link http://example.com/node/4/?authkey=5a5bc814a605658e33099cb4bdbcd5c7fe69fe09ef77faee0220905f35e62899 can use the same authkey and delete the node by adding "delete" to the link : http://example.com/node/4/delete?authkey=5a5bc814a605658e33099cb4bdbcd5c7fe69fe09ef77faee0220905f35e62899

✨ Feature request
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States shadcn

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ͺπŸ‡ΈSpain tunic Madrid

    This is a very old report. Currently, the module allows to select with operations are enabled for a content type, so admins can enable view but no delete. Not perfect but at least allows to expose content without the risk of being deleted.

    However, would be interesting to have this. Patches ar welcome.

Production build 0.71.5 2024