How to fix: Meta Refresh Redirect Detected
Meta refresh redirects can be abused for open redirect attacks and phishing.
Why it matters
Meta refresh redirects bypass standard navigation controls.
Meta refresh tags automatically redirect users after a delay. Unlike server-side redirects, they execute in the browser.
How to fix it
- 1Replace meta refresh with server-side 301/302 redirects.
- 2Never allow user-controlled input in meta refresh URLs.
Code examples
Server redirect
import { redirect } from 'next/navigation';
redirect('/new-page');References
Detected automatically by VulnRadar. The check id is meta-refresh, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Meta Refresh Redirect Detected?
- VulnRadar rates this low severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id meta-refresh, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Meta Refresh Redirect Detected map to?
- It maps to CWE-601. In the OWASP Top 10 it falls under A01:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.