We try our best to keep ZeroClipboard secure, but there are some rules that you should follow to keep your site safe.

Basically, if an attacker gets access to the main window/global object via an XSS exploit, it's pretty much an instant "GAME OVER" unless ALL of the following are true:

1. The ZeroClipboard object itself is not globally accessible.
2. The ZeroClipoard.Client object itself is not globally accessible.
3. The ZeroClipboard.Client.prototype object itself is not globally accessible.
4. No ZeroClipboard.Client instances are globally accessible.
5. No callback functions for dispatched ZeroClipboard events are globally accessible.
6. If a variable is used to set the path to the SWF via ZeroClipboard.Client#setMoviePath, that variable must not be globally accessible.

1. Having ZeroClipboard.Client instances globally accessible (versus encapsulated in a closure). This allows an attacker to manually call a client's setText method and inject their own text.
2. As with all globally accessible functions in JavaScript, any globally accessible callback functions (hooked to events) can be overridden by an attacker. This isn't terribly dangerous but could be annoying.
3. If we add a "dataRequested" event (see #46), then users would need to apply the safety precautions mentioned in_both_ of the aforementioned examples to avoid allowing an attacker to inject their own text.
4. Overriding any of the ZeroClipboard, ZeroClipboard.Client, or ZeroClipboard.Client.prototype properties or methods, if globally accessible.

If you find any security holes, please submit a pull request, or file an issue. We will be very appreciative.