How to fix: postMessage receiver does not validate origin
A message event listener processes messages without checking event.origin, accepting messages from any window.
Why it matters
Without origin validation, any malicious page in the same browser can send postMessage events to your page and have them processed, potentially triggering privileged actions, passing tokens, or modifying application state.
Every postMessage receiver must validate event.origin against a trusted allowlist before processing the message.
How to fix it
- 1Add an origin check: if (event.origin !== "https://trusted.example.com") return;
- 2Use a Set of allowed origins for multiple trusted partners
- 3Never use "*" as targetOrigin when sending sensitive data
Code examples
Validate origin in postMessage handler
// Unsafe: accepts messages from any origin
window.addEventListener('message', (event) => {
processMessage(event.data);
});
// Safe: check origin before processing
window.addEventListener('message', (event) => {
if (event.origin !== 'https://trusted.example.com') return;
processMessage(event.data);
});References
Detected automatically by VulnRadar. The check id is postmessage-origin, 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 postMessage receiver does not validate origin?
- 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 postmessage-origin, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does postMessage receiver does not validate origin map to?
- It maps to CWE-346. In the OWASP Top 10 it falls under A05: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.