How to fix: postMessage() With Wildcard Origin
postMessage called with * origin target.
Why it matters
Sensitive data sent to any listening window.
Using * as target origin means any page can receive the message.
How to fix it
- 1Specify the exact target origin instead of *.
Code examples
Replace "*" targetOrigin with explicit origin
// BAD: "*" sends to any origin
// window.parent.postMessage(data, "*");
// GOOD: explicit trusted origin
window.parent.postMessage(data, "https://partner.example.com");
// Receiver: always validate origin
window.addEventListener("message", (e) => {
if (e.origin !== "https://trusted.example.com") return;
handleMessage(e.data);
});References
Detected automatically by VulnRadar. The check id is postmessage-star-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() With Wildcard 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-star-origin, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does postMessage() With Wildcard 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.