How to fix: Missing <meta charset> Declaration
The HTML document does not declare a character set via <meta charset>. Without an explicit charset, older browsers could be tricked into an encoding (e.g. UTF-7) that enables reflected content to execute as script.
Why it matters
Largely historical: modern browsers no longer support UTF-7 auto-detection, so the practical XSS risk is minimal. Still worth declaring for correctness and to avoid mojibake rendering.
Declare <meta charset="utf-8"> within the first 1024 bytes of the document, or set charset via the Content-Type header.
How to fix it
- 1Add <meta charset="utf-8"> as the first element inside <head>.
Code examples
Declare charset in HTML meta tag
<!DOCTYPE html>
<html lang="en">
<head>
<!-- Must be within first 1024 bytes of the document -->
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Page Title</title>
</head>References
Detected automatically by VulnRadar. The check id is charset-meta-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Missing <meta charset> Declaration?
- VulnRadar rates this info severity in the headers 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 charset-meta-missing, 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.