The vulnerability stems from improper authorization checks in bulk action handlers. The security advisory explicitly lists specific bulk operations (publish/unpublish, sticky/unsticky, promote/demote) that required additional permission checks. These operations are implemented as action plugins in the Node module, each with an access() method controlling permissions. The vulnerability existed because these methods did not require the 'administer nodes' permission, allowing users with basic editing rights to perform privileged bulk operations. During exploitation, these access control methods would be invoked and appear in stack traces when unauthorized bulk operations are attempted.