Weak Referrer Policy
Controls how much data about "where the user came from" is sent to the next website they visit.
Business Risk
Privacy Leak: If a user resets their password at `yoursite.com/reset-password?token=123` and then clicks a link to an external blog, that blog receives the full URL (including the token) in the Referrer header. They could potentially hijack the account. `strict-origin-when-cross-origin` fixes this by stripping the path/query parameters for external requests.
Technical Details
This header is critical for sites with sensitive URL parameters. `no-referrer` is the most private but breaks analytics. `strict-origin-when-cross-origin` is the modern "safe default" used by most browsers today even if unset, but you should set it explicitly to ensure coverage.
Remediation Guide
External References
Verify Your Fix
Applied the configuration change? Run a live scan to confirm the vulnerability is patched.