Submitted by glcanvas, also found by libratus, adriro, and hansfriese
https://github.com/rabbitholegg/quest-protocol/blob/8c4c1f71221570b14a0479c216583342bd652d8d/contracts/Quest.sol#L13
https://github.com/rabbitholegg/quest-protocol/blob/8c4c1f71221570b14a0479c216583342bd652d8d/contracts/Quest.sol#L44
https://github.com/rabbitholegg/quest-protocol/blob/8c4c1f71221570b14a0479c216583342bd652d8d/contracts/Quest.sol#L96-L118
https://github.com/rabbitholegg/quest-protocol/blob/8c4c1f71221570b14a0479c216583342bd652d8d/contracts/RabbitHoleReceipt.sol#L95-L104
https://github.com/rabbitholegg/quest-protocol/blob/8c4c1f71221570b14a0479c216583342bd652d8d/contracts/QuestFactory.sol#L215-L229
Might be impossible to claim rewards by users. And admins must distribute tokens manually and pay fee for this. On a huge amount of participants this leads to huge amount of fees.
Lets consider QuestFactory. It has:
Which responsible for mint tokens for users.
Then consider createQuest function. Here we pass rabbitholeReceiptContract into Quest.
In Quest this field is immutable.
Now lets consider next case:
Possible solution here is change minterAddress in the original RabbitHoleReceipt contract and manually mint tokens by admin, but it will be too expensive and the company may lost a lot of money.
In QuestFactory contract in the function mintReceipt  the rabbitholeReceiptContract must be fetched from the quest directly.
To Quest Add:
Modify mintReceipt function in QuestFactory like:
waynehoover (RabbitHole) disagreed with severity and commented:
kirk-baird (judge) decreased severity to Medium and commented:
