This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Category:OWASP PHP AntiXSS Library Project"

Jump to: navigation, search
(Reverting to last version not containing links to
Line 1: Line 1:
== Introduction ==
== Introduction ==

Revision as of 18:28, 27 May 2009


AntiXSS is a class for use with PHP 5+ that helps to reduce XSS (cross-site scripting) vulnerabilities by automatically encoding output to behave only as intended.


NOTE: This library will eventually replaced by the ESAPI for PHP port. That effort is not complete as yet. The actual API will not change dramatically between AntiXSS library and ESAPI for PHP.


  • PHP5 and above
  • mb_string PHP extension


  1. Make sure the mb_string extension is available with your PHP installation. If you are using Apache on Windows, this can most likely be done by adding (or un-commenting) a line in your php.ini file. On other platforms, you may need to recompile PHP. See [1] for more information.
  2. To make the code available to your program, include the owasp.antixss.php file, using a line like this: require_once "/path/to/owasp.antixss.php";
  3. It is not necessary to instantiate the class, though you may if you wish. Instead, make calls using the Scope Resolution Operator (::), like this: echo AntiXSS::HTMLEncode($myOutput);



Hello, <php echo AntiXSS:HTMLEncode($nameOfMyUser); ?>!


... alert(myFunction('<?php echo AntiXSS:JavaScriptEncode($myVariable); ?>'); ...


...<?php echo AntiXSS::URLEncode($myQueryStringValue); ?> ...


<myelement myattribute="<?php echo AntiXSS::XMLAttributeEncode($myAttributeValue); ?>"><?php echo AntiXSS::XMLEncode($myElementValue); ?></myelement >


Downloads are not yet available.

  • owasp.antixss.php
  • demo.owasp.antixss.php



The AntiXSS class will use any character encoding supported by libmbfl, the library upon which the mbstring functions are based, with the exception of 7bit and BASE64.

A list of supported character sets is available at [2]

The Owasp AntiXSS class utilizes the following encodings: UTF-32, HTML-ENTITIES

Typically, your doctype definition will match the encoding of your source files and your database source. If you run into issues where some characters don't display or display wrong, check the encoding of every data source and file involved.

And particularly if you wish to output extended or multibyte characters from within your source files, make sure the encoding of all files involved matches the output format, unless you will be handling your conversions manually using mb_convert_encoding.

This category currently contains no pages or media.