How to fix: Suspicious Content in Open Graph Tags
Open Graph meta tags contain suspicious content that could indicate injection.
Why it matters
Malicious OG content can be exploited by link preview services.
Some preview renderers process OG values in ways that can be exploited.
How to fix it
- 1Sanitize all Open Graph tag content.
- 2Validate og:url and og:image point to your own domains.
- 3Never include user-controlled input in OG tags without encoding.
Code examples
Safe OG tags
<meta property="og:url" content="https://example.com/page" />
<meta property="og:image" content="https://example.com/image.jpg" />References
Detected automatically by VulnRadar. The check id is opengraph-injection, 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 Suspicious Content in Open Graph Tags?
- VulnRadar rates this medium 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 opengraph-injection, 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.