Skip to main content

How to fix: Insecure Base Tag Detected

The page uses a <base> tag with an HTTP URL, making all relative URLs resolve insecurely.

Why it matters

All relative links, scripts, images resolve against the insecure base URL.

The HTML <base> tag sets the base URL for all relative URLs in the document.

How to fix it

  1. 1Change the <base> tag to use HTTPS.
  2. 2Remove the <base> tag if not needed.
  3. 3Implement CSP base-uri directive.

Code examples

CSP restriction

text
Content-Security-Policy: base-uri 'self'

References

Detected automatically by VulnRadar. The check id is base-tag-insecure, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is Insecure Base Tag Detected?
VulnRadar rates this high 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 base-tag-insecure, which stays the same between runs so you can filter, diff, or gate CI on it.

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.

Propose a checkHow a check is built

Scan your own site for insecure base tag detected

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Insecure Base Tag Detected | VulnRadar