How to fix: postMessage with wildcard targetOrigin
postMessage() is called with "*" as the targetOrigin, sending the message to any origin.
Why it matters
Using "*" as the targetOrigin allows any malicious page in the same browser session to receive the message, leaking tokens, authentication data, or application state to attacker-controlled frames.
When a postMessage call uses "*", any window open in the browser (including cross-origin malicious pages) can receive the message payload.
How to fix it
- 1Replace "*" with the exact expected target origin (e.g., "https://partner.example.com")
- 2Validate event.origin in the message receiver before processing
Code examples
Always specify targetOrigin in postMessage
// BAD: wildcard targetOrigin leaks data to any origin
window.parent.postMessage({ token: authToken }, "*");
// GOOD: specify exact target origin
window.parent.postMessage({ token: authToken }, "https://trusted.example.com");
// Receiver: always validate event.origin
window.addEventListener("message", (e) => {
if (e.origin !== "https://trusted.example.com") return;
// handle e.data safely
});References
Detected automatically by VulnRadar. The check id is postmessage-wildcard, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is postMessage with wildcard targetOrigin?
- VulnRadar rates this medium severity in the code 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-wildcard, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does postMessage with wildcard targetOrigin 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.