docs: update reference

[GangGreenTemperTatum]

PR Checklist 🚨

It is intended that only defined "vulnerability entry leads" should be able to create PR's (See CODEOWNERS and Core Team)

If you are not a CODEOWNER for the entry of artifact, please see our Issues and Discussions boards

Proposed changes

@AltayAkkus, sorry for the random tag but i thought this was an awesome attack vector - kudos and TY for your awesome research! 🙌

Types of changes

Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have x-referenced the appropriate issue this addresses within the projects board
• I have applied the relevant labels this PR addresses

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[github-actions]

👋 Thanks for your pull request! Please ensure appropriate labels are applied for review routing.